From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] openssh: Version bump. 10.0p2 -> 10.1p1
Date: Fri, 17 Oct 2025 10:20:29 +0200 [thread overview]
Message-ID: <20251017082029.3111069-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20251007165623.260039-1-christian.melki@t2data.com>
Thanks, applied as d0dff9b0a7369e28df1122972e63aa2028aecde7.
Michael
[sent from post-receive hook]
On Fri, 17 Oct 2025 10:20:28 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> (openssh.com seems swamped).
> https://www.openssh.com/txt/release-10.1
> Most interesting bits seems to be the moving of the
> sockets used by agent and forwarded sockets from sshd
> from /tmp to ~/.ssh/agent.
> This could mean a few changes for home directories for
> embedded machines. Plus the typical cleanup would
> now fall to the agent.
>
> Plugs CVE:
> 2025-61984: Control characters in usernames when expanding the ProxyCommand string
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20251007165623.260039-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/openssh.make b/rules/openssh.make
> index 4eb9448fd28d..f6abc9b66132 100644
> --- a/rules/openssh.make
> +++ b/rules/openssh.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_OPENSSH) += openssh
> #
> # Paths and names
> #
> -OPENSSH_VERSION := 10.0p2
> -OPENSSH_MD5 := 689148621a2eaa734497b12bed1c5202
> +OPENSSH_VERSION := 10.1p1
> +OPENSSH_MD5 := 80dd9bb00a86519934710d05903fdf07
> OPENSSH := openssh-$(OPENSSH_VERSION)
> OPENSSH_SUFFIX := tar.gz
> OPENSSH_URL := \
prev parent reply other threads:[~2025-10-17 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 16:56 [ptxdist] [PATCH] " Christian Melki
2025-10-17 8:20 ` Michael Olbrich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251017082029.3111069-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox