Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi my fist post,tons of info on the forum but still didn't find
a solution to my prob.
I am trying to harden a production system running rhel 5.4
My problem is with pam_tally2.I want pam_tally2 to lockout almost all users
after 3 failled attempts,i can do that easilly with deny=3.My problem
is that for some users or for a specific group i want pam_tally2 not to lock
their accounts not matter how many attempts they trie,to prevent a denial
of service attack.Any idea on how to do this,
Much appreciated
p.s seems that the per_user option is not working as expected,meaning
that even if i setup a faillog -m 0 username pam_tally2 overwrites that
every time i login with m=3 for all users,perhaps i am missing something here.
Perhaps a different approach is in order, do your users reside in openldap?
The ppolicy overlay is configurable to have different rules for different users or groups of users. Using ppolicy with access.conf and Denyhosts might solve most of your problem.
anomie:have read the documentation still couldn't find an answer to my problem.Thanks for the reply
frndrfoe:i was hoping to avoid openldap mainly because i have no knowledge of it.Since it seems there is no other way i will wait a few more days and if no other user answers i will have a go at it.Thanks for the reply.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.