From: ruggero rossi via ptxdist <ptxdist@pengutronix.de>
To: ruggero rossi via ptxdist <ptxdist@pengutronix.de>
Cc: ruggero rossi <rugrossi@googlemail.com>
Subject: [ptxdist] problems with openssh 10.0p1 in ptxdist 2025.05.0
Date: Thu, 5 Jun 2025 11:32:41 +0200 [thread overview]
Message-ID: <20250605113241.3733ed9b@RR-Laptop> (raw)
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
Migrating to ptxdist 2025.05.0 I got a problem with openssh 10.0p1 (or p2,
whatever is the official name).
The openssh server does not start.
Starting it manually, I get the message:
/usr/sbin/sshd-auth does not exist or is not executable
Installing /usr/sbin/sshd-auth solves the problem.
Maybe this is due to some unfortunate combination of old libc and legacy
certificates, however in the release note of openssh 10.0.p2 I read:
"this release removes the code responsible for the user authentication
phase of the protocol from the per connection sshd-session binary to a new
sshd-auth binary..... Downstream distributors of OpenSSH will need to
package the sshd-auth binary."
In case the problem is confirmed, attached there is a patch.
Best regards,
Ruggero
[-- Attachment #2: openssh10.0p2-requires-sshd-auth-binary.patch --]
[-- Type: text/x-patch, Size: 431 bytes --]
--- rules/openssh.make.org 2025-06-05 10:56:26.949816645 +0200
+++ rules/openssh.make 2025-06-05 10:57:19.878901998 +0200
@@ -108,6 +108,8 @@
/usr/sbin/sshd)
@$(call install_copy, openssh, 0, 0, 0755, -, \
/usr/sbin/sshd-session)
+ @$(call install_copy, openssh, 0, 0, 0755, -, \
+ /usr/sbin/sshd-auth)
ifdef PTXCONF_OPENSSH_SSHD_GENKEYS
@$(call install_alternative, openssh, 0, 0, 0755, /etc/rc.once.d/openssh)
endif
next reply other threads:[~2025-06-05 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 9:32 ruggero rossi via ptxdist [this message]
2025-06-05 10:14 ` Alexander Dahl via ptxdist
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=20250605113241.3733ed9b@RR-Laptop \
--to=ptxdist@pengutronix.de \
--cc=rugrossi@googlemail.com \
/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