All these resources state that /etc/ssh/sshd_config must be modified, which I can simply not allow. This shows that other people have this issue. If this is "by design" then at the very least, absolute very least, document this on the Man Page that once the MaxAuthTries has been exceeded, an account is locked out permanently until the sshd_config file is physically modified and a higher number is temporarily added.
Such behavior is not only unexpected, even if this was added to the Man Page, but also doesn't follow any Linux designs regarding lock outs. Not other lockout mechanisms react this way in Linux / Ubuntu. References Resources: Oldest resource and report of this issue is from ServerFault from 2012. How come this hasn't been resolved 13 years later? (2012?! - suggests `pam_tally2 -u <user>` which isn't a command in Ubuntu Server) https://serverfault.com/questions/415321/fix-too-many- authentication-failures (Also from 2012!) https://www.linuxquestions.org/questions/linux- security-4/sshd_config-maxauthtries-when-does-it-reset-4175423344/ Says you have to modify sshd_config: (2017 - 7 years ago) https://visser.io/2017/07/resetting-ssh-access-after-too-many- authentication-failures-for-on-google-cloud-compute-engine/ (2020 - 4 years ago) https://serverfault.com/questions/879778/ssh-logs- i-dont-understand-maximum-authentication-attempts-exceeded No answer to someone reporting this issue on RedHat forums in 2016: https://access.redhat.com/discussions/764173 Answers say you have to modify sshd_config: https://unix.stackexchange.com/questions/574090/maxauthtries-is-being- crazy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2094529 Title: Impossible to Reset MaxAuthTries After Lockout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2094529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
