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.
On systems using PAM you could add a "pam_listfile.so" line to /etc/pam.d/passwd and configure the list it only allow or deny certain users to change their password. An upgrade of the package containing /usr/bin/passwd might reset the setuid bit. That change might escape your attention unless you monitor or regularly audit file permissions.
Nice idea but that's not a method in any book. Doing that will break usage for legitimate processes that doesn't have /root/bin in it's $PATH. Besides an update will place the binary back where it belongs.
Just do chmod go-rx /usr/bin/passwd. That way users can't run the passwd program at all.
If you want some users to change their passwords, but not others, put those users in a group, make that the group associated with passwd, and set group permissions so group members can run it.
Perhaps you guys missed the subtlety of using chattr...
Once you have used chattr, the passwd command is still available...and it even looks, to the user, as if their password is changed...but the passwd program complains silently when they use passwd. No feedback results. they simply cant change their passwd, even the root user cannot, until chattr -i is issued.
and it even looks, to the user, as if their password is changed...No feedback results
I'd say that's a really bad idea. The last thing you want is someone thinking their password has been changed when it hasn't. You'll then have to field user complaints of "I changed my password but it didn't work" and so on. As well as the risk of a user changing their password because their old one had become known to others, and not realising the change had failed and then getting their account broken into.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.