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.
this is a little tweak
create a shellscript /bin/nologin
give execute rights
chmod a+x /bin/nologin
write that into it:
!#/bin/sh
echo "Restricted acces get lost"
Append the shell name into /etc/shells
...
/bin/sh
/bin/nologin
...
then create the user and specify his shell /bin/login
next time the user will try to log on... He will see "Restricted access get lost"
Just removing it will work for most programs but some complain about it.
The easiest way would be to either change the shell to /dev/null or /bin/false and then also add that entry to /etc/shells.
But that's exactly what the other two people suggested.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.