sshkey
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
sshkey [2008/12/02 15:01] – cangiani | sshkey [2022/08/05 13:20] (current) – admin | ||
---|---|---|---|
Line 2: | Line 2: | ||
You can connect to the servers using the SSH protocol without the need to insert the password every time you connect. The trick is to generate a encripted key that can be used by the systems to recognize yourself and allow your access to local resources. | You can connect to the servers using the SSH protocol without the need to insert the password every time you connect. The trick is to generate a encripted key that can be used by the systems to recognize yourself and allow your access to local resources. | ||
This behaviour can be used when you are using the Servers from the Epfl Network, but also when you connect to the server from outside the Epfl. | This behaviour can be used when you are using the Servers from the Epfl Network, but also when you connect to the server from outside the Epfl. | ||
+ | ===== Setup ===== | ||
- | ===== Ssh without password from local workstation ===== | + | ==== Generate the public/ |
+ | |||
+ | Note that this doc applies only to Unix (Mac/ | ||
- | ==== Apple Os X & Linux ==== | ||
* Login in your workstation and open a Terminal Windows (if you are using the Graphical interface) | * Login in your workstation and open a Terminal Windows (if you are using the Graphical interface) | ||
* Execute this command | * Execute this command | ||
- | $ ssh-keygen -t dsa | + | $ ssh-keygen -t ed25519 |
- | * When the system ask a name for the file **id_dsa** just press enter | + | * When the system ask a name for the file **id_ed25519**, just press enter |
- | * Do the same for the **id_dsa.pub** file | + | |
- | * cd in your .ssh directory with | + | * The system will ask your for a password. This is the password that is used to encrypt your private key file (id_ed25519) so, even if the file gets stolen, it cannot be used. Try to generate a strong password. |
- | | + | |
- | | + | |
- | | + | |
- | From now, every time you connet to a server, the server will recognize your workstation automatically (it read the ~/.ssh/authorized_keys file everytime you connect) and you can login without bothering with the password. | + | $ cat ~/.ssh/id_ed25519.pub >> ~/ |
- | ===== Ssh without password | + | From now, every time you connect to a server, the server itself will recognize your workstation automatically (it read the ~/ |
+ | In fact, since your private key is encrypted, you need to type the password to decrypt it each time you want to use it. Seems like we have just replaced the "enter remote machine password" | ||
- | ==== Apple Os X & Linux ==== | + | ==== Setup ssh-agent |
- | * Open a terminal emulation window | + | Ssh-agent is a program that keeps in memory your decrypted private ssh key and serves it to ssh when it is needed. In this way you only have to type the decryption password only once. Keeping the decrypted key (or the password) in memory is considered safer than letting the key file un-encrypted. |
- | * Execute | + | |
- | $ ssh-keygen -t dsa | + | === On desktop sessions === |
+ | All modern desktop environment (os X, Gnome, KDE), do take care automatically the ssh key decryption business and you don't have to do anything. Yahoo! | ||
- | * When the system ask a name for the file **id_dsa** just press enter | + | === On console === |
- | * Do the same for the **id_dsa.pub** file | + | If you are not on a full desktop environment (e.g. if you ssh to a machine from where you want to connect to [several] another machines), then you have to setup the ssh-agent business by hand. |
- | * cd in your .ssh directory with | + | |
- | $ cd ~/.ssh | + | The two (actually three) steps are |
+ | * launch '' | ||
- | * Execute this command | + | |
+ | |||
+ | | ||
+ | |||
+ | $ ssh-add [-t time_in_seconds] ~/ | ||
+ | |||
+ | * before logging out you have to remember to kill the ssh-agent: | ||
- | $ cat id_dsa.pub | + | $ ssh-agent -k |
- | * Open another window and from this connect | + | Since this is quite cumbersome, I suggest |
- | * cd in .ssh directory with | + | |
- | | + | < |
+ | # only for interactive shell | ||
+ | if [ "$PS1" ]; then | ||
+ | # run ssh agent if not already running | ||
+ | SSHAGENT=/ | ||
+ | if [ -z " | ||
+ | eval `$SSHAGENT -s` | ||
+ | alias ssh=' | ||
+ | trap " | ||
+ | fi | ||
+ | fi | ||
+ | </ | ||
- | * Execute | + | This will start '' |
- | + | ||
- | $ cat >> authorized_keys | + | |
- | * Now copy & paste with the mouse the key you have in the first window (something that start with sh-dss AAAAB3NzaC1k....) to the second window. | ||
- | * press the " | ||
- | * Try to connect to **lth.epfl.ch**, |
sshkey.1228226476.txt.gz · Last modified: 2008/12/02 15:01 by cangiani