Willipedia is now back online as of 5/5/2019 |
It has been several years since Willipedia closed. Please help get it updated! |
Go to the Willipedia 2.0 Project to learn more. |
Difference between revisions of "SSH"
Line 1: | Line 1: | ||
'''SSH''', which stands for "secure shell", is a way to log into a server and execute commands on a [[command line]]. | '''SSH''', which stands for "secure shell", is a way to log into a server and execute commands on a [[command line]]. | ||
− | ==Windows== | + | ==Logging in with SSH== |
+ | |||
+ | ===Windows=== | ||
1. Find and download putty.exe on this page: | 1. Find and download putty.exe on this page: | ||
Line 37: | Line 39: | ||
7. You're in! Happy computing. | 7. You're in! Happy computing. | ||
− | ==Mac/Linux== | + | ===Mac/Linux=== |
Let's say your user name is ewilliam and you want to log in to wso.williams.edu. From a [[command line]], type | Let's say your user name is ewilliam and you want to log in to wso.williams.edu. From a [[command line]], type | ||
Line 44: | Line 46: | ||
Enter your password when prompted. If it's your first time and you get a warning about host keys, just say "yes". | Enter your password when prompted. If it's your first time and you get a warning about host keys, just say "yes". | ||
+ | |||
+ | ==Logging in without a password== | ||
+ | |||
+ | Note: Logging in without a password will save you a few seconds out of every day. It comes however, with an added security risk: if someone compromises your | ||
+ | machine, they can then log into WSO with your account. If you are willing to bear this responsibility, then read on. | ||
+ | |||
+ | Anyway, enough chit-chat. Here's how to do it: | ||
+ | |||
+ | ===Mac/Linux=== | ||
+ | Adapted from http://bumblebee.lcs.mit.edu/ssh2/. | ||
+ | |||
+ | 1. Open a [[command line]] | ||
+ | |||
+ | 2. Generate a public key and a private key. We'll copy the public key over to the server later. | ||
+ | |||
+ | ssh-keygen -t rsa -f ~/.ssh/id_rsa | ||
+ | |||
+ | 3. When it says something like | ||
+ | |||
+ | Enter passphrase (empty for no passphrase): | ||
+ | |||
+ | Just press return. | ||
+ | |||
+ | 4.Let's copy the public key to WSO. Type | ||
+ | |||
+ | scp .ssh/id_rsa.pub user@wso:~/.ssh/. | ||
+ | |||
+ | 5. Cruise over to the WSO server: | ||
+ | |||
+ | ssh user@wso.williams.edu | ||
+ | |||
+ | 6. Hop into the SSH directory: | ||
+ | |||
+ | cd .ssh | ||
+ | |||
+ | 7. Append the key to your list of authorized keys: | ||
+ | |||
+ | cat id_rsa.pub >> authorized_keys2 | ||
+ | |||
+ | 8. Change permissions: | ||
+ | |||
+ | chmod 640 authorized_keys2 | ||
+ | |||
+ | 9. Kill the key. | ||
+ | |||
+ | rm id_rsa.pub | ||
+ | |||
+ | All done! Now you can SSH and SCP to WSO without a password. | ||
+ | |||
+ | ===Windows=== | ||
+ | This link will give you some background about public-key authentication, and how to do it with PuTTY: | ||
+ | |||
+ | http://the.earth.li/~sgtatham/putty/0.54/htmldoc/Chapter8.html#8 | ||
+ | |||
+ | A few tips: | ||
+ | |||
+ | * Use RSA | ||
+ | * Your authorized keys file is called .ssh/authorized_keys2 | ||
+ | |||
+ | Best of luck! |
Revision as of 00:53, May 5, 2006
SSH, which stands for "secure shell", is a way to log into a server and execute commands on a command line.
Contents
Logging in with SSH
Windows
1. Find and download putty.exe on this page:
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
The program doesn't need to be installed; just open the file you downloaded whenever you want to run PuTTY.
2. Open putty.exe
3. Enter "wso.williams.edu" (or whatever) for the host, and "SSH" for the protocol.
4. Click "Open"
5. Enter your WSO login and password when prompted.
6. If this is your first time connecting from this computer, you might get a message like this:
The server's host key is not cached in the registry. You have no guarantee that the server is the computer you think it is. The server's key fingerprint is: ssh-rsa 1024 7b:e5:6f:a7:f4:f9:81:62:5c:e3:1f:bf:8b:57:6c:5a If you trust this host, hit Yes to add the key to PuTTY's cache and carry on connecting. If you want to carry on connecting just once, without adding the key to the cache, hit No. If you do not trust this host, hit Cancel to abandon the connection.
If this is your first time, don't sweat it, just say Yes. If you get this message and this is not your first time SSH'ing from this machine, you might drop us a line. For more information about host keys, read this page:
http://the.earth.li/~sgtatham/putty/0.55/htmldoc/Chapter2.html
7. You're in! Happy computing.
Mac/Linux
Let's say your user name is ewilliam and you want to log in to wso.williams.edu. From a command line, type
ssh ewilliam@wso.williams.edu
Enter your password when prompted. If it's your first time and you get a warning about host keys, just say "yes".
Logging in without a password
Note: Logging in without a password will save you a few seconds out of every day. It comes however, with an added security risk: if someone compromises your machine, they can then log into WSO with your account. If you are willing to bear this responsibility, then read on.
Anyway, enough chit-chat. Here's how to do it:
Mac/Linux
Adapted from http://bumblebee.lcs.mit.edu/ssh2/.
1. Open a command line
2. Generate a public key and a private key. We'll copy the public key over to the server later.
ssh-keygen -t rsa -f ~/.ssh/id_rsa
3. When it says something like
Enter passphrase (empty for no passphrase):
Just press return.
4.Let's copy the public key to WSO. Type
scp .ssh/id_rsa.pub user@wso:~/.ssh/.
5. Cruise over to the WSO server:
ssh user@wso.williams.edu
6. Hop into the SSH directory:
cd .ssh
7. Append the key to your list of authorized keys:
cat id_rsa.pub >> authorized_keys2
8. Change permissions:
chmod 640 authorized_keys2
9. Kill the key.
rm id_rsa.pub
All done! Now you can SSH and SCP to WSO without a password.
Windows
This link will give you some background about public-key authentication, and how to do it with PuTTY:
http://the.earth.li/~sgtatham/putty/0.54/htmldoc/Chapter8.html#8
A few tips:
- Use RSA
- Your authorized keys file is called .ssh/authorized_keys2
Best of luck!