Comments on: How to Lock and Unlock User After Failed SSH Logins

By: Amar Nayak

Amar Nayak — Thu, 01 Jun 2023 04:29:21 +0000

Thanks for the very helpful article…

I see lots of SSH failed login attempts on my Linux server logs daily, I hope with this solution I can completely block such login attempts and secure my SSH box from unwanted authentications…

By: bread of wakanda

bread of wakanda — Wed, 11 Sep 2019 05:21:02 +0000

what if i have a user who keeps entering the wrong password and keeps getting locked and every single day i have to unlock him .. is there any way by which i can keep that specific user out of pam policy so that he never gets locked but others can get locked?

By: Akio Crimson

Akio Crimson — Wed, 06 Mar 2019 20:52:22 +0000

Thanks for this info. I had to come up with something because when I logged in today, it said there were 43,945 failed login attempts to root. So clearly someone set up a server in china to try to brute force their way in. I set the unlock_time in mine to 24 hours after 2 failed attempts.

By: shuja

shuja — Thu, 24 Jan 2019 12:24:33 +0000

@josh and ravi can you please tell how to make this lock option permanent so that reboot should not clear the lock also please let me know how can i apply this policy on 100 servers easily.

By: Aaron Kili

Aaron Kili — Thu, 24 Jan 2019 07:54:45 +0000

In reply to Josh.

@Josh

Many thanks for sharing this, will read more about this, and also find out how to make the setting persistent even after a reboot.