securing_remote_ssh_access
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
securing_remote_ssh_access [2013/01/05 06:06] – [Disable Root Logins] 206.174.106.118 | securing_remote_ssh_access [2013/01/05 06:07] – [Disable Root Logins] 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 | + | - If you are doing this change remotely, open another |
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. |
securing_remote_ssh_access.txt · Last modified: 2013/01/28 17:55 by 142.103.194.1