Differences

This shows you the differences between two versions of the page.

--- securing_remote_ssh_access [2013/01/05 06:07] – [Disable Root Logins] 206.174.106.118
+++ securing_remote_ssh_access [2013/01/28 17:55] (current) – 142.103.194.1
@@ Line 1: / Line 1: @@
-====== Securing Remote SSH Access ======
+====== Securing Remote Secure Shell (SSH) Access ======
 If you need to login to your node using SSH remotely, the following will help you avoid unauthorized access to your node.
@@ Line 27: / Line 27: @@
 The default SSH port 22 is where anything and everything will try when looking for Linux and Unix hosts to compromise.
-If you currently have port 22 open to the world, as root ''tail -f /var/log/secure'' to see who passing by has been "knocking on your door". ''Ctrl C'' to exit.
+If you currently have port 22 open to the world, as root ''tail -f /var/log/secure'' to see who passing by has been "knocking on your door", you'll more than likely see attempts scrolling by. ''Ctrl C'' to exit.
 Using a non-standard port will avoid most of the attention. In this example we'll use port 22500. Any high port number of your choice is generally OK.
@@ Line 33: / Line 33: @@
 There are two ways of doing this:
   - In some routers, the port forwarding configuration allows you to redirect target port. For example port 22500 externally can be mapped to port 22 internally to your IRLP system.
   - If your router does not support redirecting the target port, the configuration of sshd can be changed to listen on a non-standard port. As root edit ''/etc/ssh/sshd_config'', find the line with ''Port 22
-'' and under it on a new line add ''Port 22500''. Save the file, and restart sshd ''/etc/init.d/sshd restart''. Update the port forwarding configuration in your router to use the new port. If you are already forwarding 22, remember to remove it once you have tested connecting to the new port number. By leaving Port 22 enabled in sshd you can still use this port on your internal network for convenience, or you can take it out all together if you have no need for this.
+'' and under it on a new line add ''Port 22500''. Save the file, and restart sshd ''/etc/init.d/sshd restart''. Restarting sshd will not disconnect an existing session.
+  - In each case preserve the port 22 forwarding you may already have in place, and add an additional port forward for the new port and test it by updating the settings in your SSH client and open a new session. Once you're happy everything is working as expected you can remove or disable forwarding for port 22, then check you can no longer connect on port 22 to be sure.