Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a VPS running Ubuntu 10.04. Because it's a VPS, I do not have physical access to it. I would like to change a couple of settings in my SSH configuration file, including the port and some security measurements. But I am afraid I will lock myself out of my server. Google couldn't tell me anything I could use to build a safety to get back in if I happen to lock myself out.
I am thinking of a rather strange way of doing it; create a cron that will run a script that replaces my sshd config file with the original one and restart ssh every 15 minutes. So if I lock myself out, that script will restore the settings within 15 minutes.
I hope someone knows a better way, where I don't have to rely on a cron.
makign things obscure theoretically will stop things hitting it, but it makes things more complicated, and with root access disabled etc, there's no real benefit. It can make people lazy and think that as the port is changed, I don't need to actually bother making it properly secure.
Starting a second sshd on a different port is a good way to test that configuration without disturbing your first one.
Changing ports to avoid attacks is fairly pointless as the SSH service is recognisable on any port. I suggest requiring key rather than password authentication on Internet-facing servers. And keep the s/w up to date.
Thank you guys, I managed to secure my SSH access without locking myself out. I have another question though about security if I may. I set up an RSA key between my server and my client, and disabled PasswordAuthentication. But I want to be able to login with my tablet if I'm on the road, in case of an emergency. Unfortunately it doesn't support RSA keys... What would be the best way to open a connection for my tablet but don't affect the security? I was thinking of using the same account I use on my client and make its password 40 characters long, set MaxAuth to 1, and use the following http://jelledepot.blogspot.nl/2011/0...ation-per.html to only enable PasswordAuthentication for that user. Would that be a good way to set it up?