I found the issue. I made a mistake somehow when resolving conflicts in
debian/patches/debian-config.patch.
As a result, we have `UsePAM no` at the moment, where it has
historically been `UsePAM yes` in Debian/Ubuntu.
This causes a different code path to be taken during auth. I.e., sshd
checks with shadow if the account is locked instead of going through
PAM.
** Changed in: openssh (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2116196
Title:
Lost SSH connection with a Questing container after upgrade to OpenSSH
10.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2116196/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
