Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Does the other machine that you're logging into allow root ssh logins? Personally, I wouldn't allow it. Can you ssh as a normal user? If so, just su from a normal user account.
Log in as a regular user and then use sudo to run root commands.
Ubuntu has disabled root logins. Even if they didn't, you should always disable root logins for ssh.
I think you've got the idea by now, I just want to stress that, after you login as a regular user with sudo access, you should run
Code:
sudo su -
to become root. Then you can alter SSHD options that you can find in '/etc/ssh/sshd_conf'. As everybody is saying, it's not a great idea to allow root to login remotely.
Dictionary attacks will target system user accounts and root account.
If only a handful of users are authorized to log into the machine using ssh, you can add their names to "AllowUsers" in /etc/ssh/sshd_config. This will disallow other logins including by system users. This is a quick and easy way to lock down ssh. One other thing to consider is to only allow the ssh-2 protocol. By default, if ssh-2 fails ssh-1 is tried. Ssh-1 has some problems so hackers will try to login with this protocol.
Dictionary attacks will target system user accounts and root account.
If only a handful of users are authorized to log into the machine using ssh, you can add their names to "AllowUsers" in /etc/ssh/sshd_config. This will disallow other logins including by system users. This is a quick and easy way to lock down ssh. One other thing to consider is to only allow the ssh-2 protocol. By default, if ssh-2 fails ssh-1 is tried. Ssh-1 has some problems so hackers will try to login with this protocol.
How to increase security with a SSHd listening to either port 80 or 8080 ? Is this Secured or Mad ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.