38,760
edits
Using SSH keys in Linux/en: Difference between revisions
Updating to match new version of source page
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
| Line 88: | Line 88: | ||
Assuming you installed your key pair in one of the standard locations, the <tt>ssh-add</tt> command should be able to find it, though if necessary you can explicitly add the full path to the private key as an argument to <tt>ssh-add</tt>. Using the <tt>ssh-add -l</tt> option will show which private keys currently accessible to the <tt>ssh-agent</tt>. | Assuming you installed your key pair in one of the standard locations, the <tt>ssh-add</tt> command should be able to find it, though if necessary you can explicitly add the full path to the private key as an argument to <tt>ssh-add</tt>. Using the <tt>ssh-add -l</tt> option will show which private keys currently accessible to the <tt>ssh-agent</tt>. | ||
While using <tt>ssh-agent</tt> will allow automatically negotiate the key exchange between your personal computer and the cluster, if you need to use your private key on the cluster itself, for example when interacting with a remote GitHub repository, you will need to enable ''agent forwarding''. To enable this on the [[Béluga]] cluster, you can add the following lines to your <tt>$HOME/.ssh/config</tt> file, | While using <tt>ssh-agent</tt> will allow automatically negotiate the key exchange between your personal computer and the cluster, if you need to use your private key on the cluster itself, for example when interacting with a remote GitHub repository, you will need to enable ''agent forwarding''. To enable this on the [[Béluga]] cluster, you can add the following lines to your <tt>$HOME/.ssh/config</tt> file on your personal computer, | ||
{{File | {{File | ||
|name=config | |name=config | ||