IPG Doc

User Tools

Site Tools

Trace: • scanner
sshkey

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
sshkey [2019/11/06 11:00] – adminsshkey [2022/08/05 13:20] (current) – admin
Line 12: Line 12:
   * 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
  
-  * The system will ask your for a password. This is the password that is used to encrypt your private key file (id_dsa) so that, even if the file gets stolen, it cannot be used. Try to generate a strong password.+  * 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.
  
-  * Now you have to append the content of your public key file ''~/.ssh/id_dsa.pub'' into the ''~/.ssh/authorized_keys'' on the machines where you want to be able to ssh into (e.g. if you are generating the key pair on your laptop, you might want to add the public key on the cluster lth.epfl.ch):+  * Now you have to append the content of your public key file ''~/.ssh/id_ed25519.pub'' into the ''~/.ssh/authorized_keys'' on the machines where you want to be able to ssh into (e.g. if you are generating the key pair on your laptop, you might want to add the public key on the cluster lth.epfl.ch):
  
-  $ cat ~/.ssh/id_dsa.pub | ssh USERNAME@lth.epfl.ch 'cat - >> ~/.ssh/authorized_keys'+  $ ssh-copy-id <USERNAME>@lth.epfl.ch
  
   * In our cluster, all the machines have access to the same home directory. Therefore you can use standard local copy:   * In our cluster, all the machines have access to the same home directory. Therefore you can use standard local copy:
  
-  $ cat ~/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys+  $ cat ~/.ssh/id_ed25519.pub >> ~/.ssh/authorized_keys
  
-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.... well almost! Curious? Continue reading.+From now, every time you connect to a server, the server itself will recognize your workstation automatically (it read the ~/.ssh/authorized_keys file every time you connect) and you can login without bothering with the password.... well almost! Curious? Continue reading.
  
 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" with "enter local key encryption password".   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" with "enter local key encryption password".  
Line 45: Line 45:
   $ eval `ssh-agent -s`   $ eval `ssh-agent -s`
  
-  * ask ''ssh-agent'' to manage your ''id_dsa'' key (eventually with a lifetime ''-t time_in_seconds'')+  * ask ''ssh-agent'' to manage your ''id_ed25519'' key (eventually with a lifetime ''-t time_in_seconds'')
  
-  $ ssh-add [-t time_in_seconds] ~/.ssh/id_dsa+  $ ssh-add [-t time_in_seconds] ~/.ssh/id_ed25519
  
   * before logging out you have to remember to kill the ssh-agent:   * before logging out you have to remember to kill the ssh-agent:
sshkey.1573034422.txt.gz · Last modified: 2019/11/06 11:00 by admin