2,569
edits
Changes
Jump to navigation
Jump to search
Line 38:
Line 38: − Line 47:
Line 46: − The Private Key is a file that sits on your client PC, and is sent by the SSH Client. <br>+ − The Public Key sits on the SME server. − − −
SME Server:Documentation:User Manual:Chapter1 (view source)
Revision as of 04:50, 28 September 2007
, 04:50, 28 September 2007→Shell Access
* then grant each user shell access:
* then grant each user shell access:
chsh -s /bin/bash jim
chsh -s /bin/bash jim
====SSH With Passwords====
====SSH With Passwords====
If you need to get SSH access to your server from outside the LAN (e.g. you want to get to your work server from home) then the advised method is to use Public / Private Keys.
If you need to get SSH access to your server from outside the LAN (e.g. you want to get to your work server from home) then the advised method is to use Public / Private Keys.
During Logon, the server runs a check to see if your Private Key corresponds to its stored Public key for the user that you are trying to log on as. If they don't match then the server simply drops the TCP session.
During Logon, the server runs a check to see if your Private Key corresponds to its stored Public key for the user that you are trying to log on as.
If they don't match then the server simply drops the TCP session. There is no opportunity for a cracker to try brute forcing your root password.
Setup your keys with the information at [[:SSH_Public-Private_Keys]]
Setup your keys with the information at [[:SSH_Public-Private_Keys]]
When you have SSH Keys working, the server Admin can disable logging in using passwords.
When you have SSH Keys working, the server Admin can disable logging in using passwords.