Bug#1077765: openssh: can't be started by ssh.socket anymore

Le 02/08/2024 à 00:12, Colin Watson a écrit :
> 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.

Dear maintainers,

I confirm that this new upload fixes the problem.

Thank you for acting so quickly ! :)

Regards,