I tried many other things to reproduce this bug:

- looks like the reporter had this happen in a Digital Ocean VM. I tried that 
too, going through the openssh upgrades all the way to 13.7, changing the port 
to 2240, and it just worked
- tried ipv4 and ipv6
- then noted I was doing this all via ssh, which could interfere with the 
troubleshooting. Went back to local lxc and used "lxc console" instead of an 
ssh connection. It also worked
- then I used unattended-upgrades itself. I configured the system to bump the 
priority of openssh in noble-proposed, and configured unattended-upgrades to 
also consider proposed. It upgraded openssh-server without issues, on the 
different port, and I could ssh in after
- finally, same as above, but I did not restart openssh (or the socket) after 
changing the port to 2240. I let unattended-upgrades do it, to the version in 
proposed. It also worked.

I'm out of ideas here. The only case where I could reproduce something
similar to what was reported here is if I let the new configuration file
from the package overwrite my local changes, but even then, all that
would happen is ssh/systemd listening again on port 22 instead of my
custom port. If you guys had a firewall on port 22 or something like
that, it could explain the system no longer being reachable, but the log
from comment #23 disproves that theory for that user at least.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2087551

Title:
  OpenSSH server config broken on unattended update

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2087551/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to