Yes, I can understand the frustration here. The sshd socket activation feature in Ubuntu has evolved since it was first introduced in 22.10, and is finally settling now. However, I think this patch was still important to make so that we could fix bug 2080216, and to align the systemd unit defaults with the non-socket activated defaults in sshd.
I think a large part of the misunderstanding here is around systemd socket's ListenStream= option itself. Setting e.g. ListenStream=1234 has *always* meant "listen on port 1234 on ipv6", and "depending on the value of BindIPv6Only= this might result in the service being available via both IPv6 and IPv4 (default) or just via IPv6." [1] Hence, while adding custom overrides in /etc/systemd/systemd/ssh.socket.d/ etc. has always been supported, it is an advanced use case, and should be done with care. Most users should use the ListenAddress, Port, and AddressFamily options in /etc/ssh/sshd_config.d/ directly. In other words, if one wanted to add an override and ensure that sshd is listening on port 1234 on ipv4, it's more accurate to use ListenStream=0.0.0.0:1234 (or ListenStream=[::]:1234 for ipv6), not ListenStream=1234. Again, I understand the frustration, but I hope the information above provides helpful detail and context around the issue. [1] https://www.freedesktop.org/software/systemd/man/latest/systemd.socket.html#ListenStream= -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2118912 Title: openssh-server unavailable after upgrade to 1:9.6p1-3ubuntu13.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2118912/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
