SSH Keys: Difference between revisions

Jump to navigation Jump to search
no edit summary
(warn non-default key names require -i)
No edit summary
Line 115: Line 115:


<!--T:21-->
<!--T:21-->
Once your public key is loaded into CCDB this way, you can use it to login to any of our clusters. However, our OpenStack cloud systems cannot access the keys entered in the CCDB.
Once your public key is loaded into CCDB this way, you can use it to log in to any of our clusters. However, our OpenStack cloud systems cannot access the keys entered in the CCDB.


<!--T:40-->
<!--T:40-->
Line 158: Line 158:


<!--T:48-->
<!--T:48-->
When you generate a key the default settings are usually sufficient.  However, here are a few options which may be of interest.  We demonstrate these options here using <code>ssh-keygen</code> as described in [[Using SSH keys in Linux]], but the same options are available if you are using a graphical interface as described in [[Generating SSH keys in Windows]].
When you generate a key, the default settings are usually sufficient.  However, here are a few options which may be of interest.  We demonstrate these options here using <code>ssh-keygen</code> as described in [[Using SSH keys in Linux]], but the same options are available if you are using a graphical interface as described in [[Generating SSH keys in Windows]].
* You can specify a comment for the key, which may be helpful if you have multiple keys:
* You can specify a comment for the key, which may be helpful if you have multiple keys:
  ssh-keygen -C 'Alliance systems'
  ssh-keygen -C 'Alliance systems'
rsnt_translations
56,420

edits

Navigation menu