securing_remote_ssh_access
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
securing_remote_ssh_access [2013/01/05 06:01] – [Disable Root Logins] 206.174.106.118 | securing_remote_ssh_access [2013/01/05 06:25] – [Port 22] 206.174.106.118 | ||
---|---|---|---|
Line 19: | Line 19: | ||
- As root edit ''/ | - As root edit ''/ | ||
- Now you can either set a password on the IRLP '' | - Now you can either set a password on the IRLP '' | ||
+ | - If you are doing this change remotely, open another SSH session and test logging in as repeater or with your own user account, and switching to the root account before you close your current session. Otherwise you could potentially lock your self out of the system until you can gain access to the console to straighten things out. | ||
It is also a good practice to avoid using the root account unless you really need to be the super user to do something, one typo can hose an entire system before you know it's even happened. I managed to wipe most of the file system on a Unix system once, luckily it was on a test system, and with the OS install CD and yesterdays backup tape in hand I had the system restored to its previous state with-in a couple hours. If you have no disaster recovery plan, you can spend hours or even days piecing a system back-together. | It is also a good practice to avoid using the root account unless you really need to be the super user to do something, one typo can hose an entire system before you know it's even happened. I managed to wipe most of the file system on a Unix system once, luckily it was on a test system, and with the OS install CD and yesterdays backup tape in hand I had the system restored to its previous state with-in a couple hours. If you have no disaster recovery plan, you can spend hours or even days piecing a system back-together. | ||
Line 26: | Line 27: | ||
The default SSH port 22 is where anything and everything will try when looking for Linux and Unix hosts to compromise. | 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 '' | + | If you currently have port 22 open to the world, as root '' |
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. | 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 32: | Line 33: | ||
There are two ways of doing this: | 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. | + | - 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 ''/ | - 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 ''/ | ||
- | '' | + | '' |
+ | - In each case preserve |
securing_remote_ssh_access.txt · Last modified: 2013/01/28 17:55 by 142.103.194.1