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.
DenyUsers? or, better AllowUsers? man sshd_config
Anyway, why would you need root access to ssh? isn't it better to allow one user to access ssh and then use sudo/su when need root access?
Alternatively (or additionally), you could give the samba users nologin shells.
# chsh -s /sbin/nologin user_here
I don't use samba, but I don't see why a valid shell would be required. (However, if I am mistaken, then my advice is wrong. )
This is the way to go if your concerns are the samba users only.
If you dont want any other user then root, use Allow/DenyUsers
Also, when you create a samba user, it does need a system user.
BUT (and this is important to know) you do not need to set a password on the system user account.
This automatically does deny ssh access as empty password logins are denied by ssh.
Bear in mind setting the shell to nologin does not prevent non-shell ssh access, like portforwarding. And there's a nice little DoS using that. To block ALL types of ssh access, you need to use Allow/Deny users
And you should not allow root ssh logins. If you allow root logins, an attacker need only guess the root password. You should allow a user to login to ssh, and then su to root. And make the root password different to the user's password. That way, an attacker has to guess a username, a user password, and a root password.
Bear in mind setting the shell to nologin does not prevent non-shell ssh access, like portforwarding. And there's a nice little DoS using that. To block ALL types of ssh access, you need to use Allow/Deny users
And you should not allow root ssh logins. If you allow root logins, an attacker need only guess the root password. You should allow a user to login to ssh, and then su to root. And make the root password different to the user's password. That way, an attacker has to guess a username, a user password, and a root password.
Yes, forgot to mention the non shell ssh access (-N option). Good you mentioned that!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.