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
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.
Package: openssh
Version: 1:9.8p1-1
Severity: serious
Dear maintainers,
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 unreacha
3 matches
Mail list logo
