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

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 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.

Severity set to serious since it can render machine where ssh.socket is 
enabled unreachable after an upgrade (before ssh.service is restarted, 
which needs physical access).

Regards,