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.
Although it is good practice to have it so that only a secondary user can ssh in. As in only "admin" can ssh in, and then you have to su into root. It makes it so that if an ssh bot gets it, it still doesn't have root control of your system.
Distribution: BeOS, BSD, Caldera, CTOS, Debian, LFS, Mac, Mandrake, Red Hat, Slackware, Solaris, SuSE
Posts: 1,761
Rep:
I added these to my /etc/ssh/sshd_config file, tried to connect SSH to localhost as normal user and was denied, but root was allowed. For explaination see man sshd_config.
Code:
DenyUsers ALL
AllowUsers root
Restart sshd.
Code:
# kill -HUP `cat /var/run/sshd`
It's a best practice you connect SSH as a normal user, then after connected to remote host either su to root or use sudo.
p.s. I see bbonifield already replied, I was too slooowwww.
I want to deepen the security on ssh in such away that only root can do ssh.
Interestingly, your approach for "deepen[ing] security" is going to have exactly the opposite effect.
If you insist on going forward with this, you're going to want to enable pubkey authentication and turn all other forms of authentication off. That will at least offer some protection from brute force attacks against the one account that obviously exists on the system: root.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.