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.
It's a basic practice to not allow root logins on any networked service, to minimize risks. Especially when there are workable, secure alternatives (sudo) you shouldn't enable root logins.
Private/public key is preferable, because sshd checks if the key belongs to you. It encrypts a "challenge" using your public key which can only be "answered" by your private key, so it doesn't need stuff like passwords to travel over a hostile network.
Like unspawn said. One (of many) good reasons never to allow root to login is that a hacker only needs to guess the password to gain access. This is sort of different for SSH but ftp and telnet fall under this. Without root access, a hacker has to guess a username AND password.
I know that for services other than ssh, you better don't use root login.
But do think that, if and when breaking into the ssh connection, there is the best chance to capture and exploit the first part of communication = user/pw authorization, or is it equally exploitabale anytime during connection?
Do you think that leaving idle ssh connection on for a long time 1day or more, poses the treat for exploit?
It's a basic practice to not allow root logins on any networked service, to minimize risks. Especially when there are workable, secure alternatives (sudo) you shouldn't enable root logins.
Private/public key is preferable, because sshd checks if the key belongs to you. It encrypts a "challenge" using your public key which can only be "answered" by your private key, so it doesn't need stuff like passwords to travel over a hostile network.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
