rsnt_translations
56,420
edits
SSH Keys: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
<!--T:12--> | <!--T:12--> | ||
PK is based on a <i>keypair</i> | PK is based on a <i>keypair,</i> which consists of a private part, to be kept secret, and a public part, which can be distributed freely. | ||
Anyone can use the public key to encode a message, but the message can only be decoded with the private part. This is why PK is sometimes described as <i>asymmetric encryption</i> | Anyone can use the public key to encode a message, but the message can only be decoded with the private part. This is why PK is sometimes described as <i>asymmetric encryption.</i> | ||
<!--T:13--> | <!--T:13--> | ||
| Line 45: | Line 45: | ||
The specific process to generate an SSH key pair depends on the operating system you use. For the Windows PuTTY or MobaXterm clients, | The specific process to generate an SSH key pair depends on the operating system you use. For the Windows PuTTY or MobaXterm clients, | ||
see [[Generating SSH keys in Windows]]. For a Unix-like environment (Linux, Mac, Windows Subsystem for Linux or Cygwin), see [[Using SSH keys in Linux]]. | see [[Generating SSH keys in Windows]]. For a Unix-like environment (Linux, Mac, Windows Subsystem for Linux or Cygwin), see [[Using SSH keys in Linux]]. | ||
In addition if you are using the cloud, OpenStack provides a method for creating keypairs: See the [[Cloud_Quick_Start#SSH_key_pair| | In addition if you are using the cloud, OpenStack provides a method for creating keypairs: See the [[Cloud_Quick_Start#SSH_key_pair|SSH key pair]] section on the Cloud Quick Start page. | ||
== Installing your key == <!--T:17--> | == Installing your key == <!--T:17--> | ||
| Line 229: | Line 229: | ||
If you discover that your SSH key has been compromised, it is <i>imperative</i> that you take immediate action. | If you discover that your SSH key has been compromised, it is <i>imperative</i> that you take immediate action. | ||
* Replace the compromised key with a new one to ensure that you can connect securely to Alliance services. | * Replace the compromised key with a new one to ensure that you can connect securely to Alliance services. | ||
* Remove the compromised key from | * Remove the compromised key from <i>all</i> services (Alliance or other) to prevent unauthorized access or data breaches. | ||
<!--T:55--> | <!--T:55--> | ||