SSH Keys For Passwordless Entry
Use this at your own risk. We do not recomment this unless you have a reason. If the machine you connect from is compromised in any way, the attacker can get into your CSE account.
Possible Reasons to use this:
- You are a TA and want to connect to your TA account without needing to remember the password.
- You teach a class and want to connect to the class account without needing to remember the password.
- If you co-teach a class and both want to share the class account without wanting the password.
- Batch or grid processing on our linux labs during idle times.
On the machine you want to connect from
- Run: ssh-keygen -d
This will create a .ssh directory with a public and private key
- Verify the permissions on the id_dsa private key are private (-rw-------).
- Verify the permissions of your .ssh directory is world readable (chmod 755 .ssh)
- Verify the permissions on the is_dsa.pub public key are world readable (-rw-r--r-- , or chmod 644 id_dsa.pub)
- No other files in .ssh need to be world readable except id_dsa.pub
On the machine you are connecting to
- Create a file called authorized_keys2 in your .ssh directory that contains the contents ofyour id_dsa.pub
- Verify the permissions ofauthorized_keys2 is private (-rw------- , or chmod 600 authorized_keys2)
- Make sure there are no line feeds in this file.
If you are using this within the CSE systems, follow all the steps on arctic.
The last step would be: cp id_dsa.pub authorized_keys2
You can now connect to CSE systems without a password.