Chris, Kevin, John, or anyone else affected: Is it possible that you changed your sshd_config without actually reloading and restarting ssh.socket, a while (hours, days, etc.) before the upgrade occurred? I am wondering if it's possible that the configuration was already broken by a local change, and the upgrade (which will call systemctl daemon-reload and systemctl restart ssh.socket) just surfaced the problem.
-- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
