On Thu, Aug 01, 2024 at 07:01:28PM +0200, Raphaël Halimi wrote: > Since the latest openssh upgrade, ssh.socket service can't start > ssh.service. > > It fails with the error message "fatal: Cannot bind any address", and gives > up after 5 tries (which is expected), leaving the machine unreachable. > > ssh.service on its own starts normally. > > This is a regression, as previous versions of ssh.socket were able to start > the service without problems. > > A simple workaround is to disable ssh.socket and enable ssh.service, but it > would be nice to have systemd socket activation working again.
My best guess is that this has something to do with the refactoring of sshd into a listener binary and a per-session binary, which touched the re-exec path that's also involved in socket activation. I'll try to figure it out, but it may take a little while. I think we should probably also add an autopkgtest for the socket activation case. Since it's not the default and not otherwise automatically tested right now, it's easy for it to break accidentally. -- Colin Watson (he/him) [cjwat...@debian.org]
