ssh_keys
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| ssh_keys [2021/06/22 16:12] – 134.190.232.18 | ssh_keys [2021/06/22 16:40] (current) – 134.190.232.18 | ||
|---|---|---|---|
| Line 48: | Line 48: | ||
| ===How SSH Keys work=== | ===How SSH Keys work=== | ||
| + | |||
| + | The following is a gross oversimplification of what is actually happening behind the scenes but it gives you the gist. | ||
| + | |||
| + | A Public Key **encrypts** data and a Private Key **decrypts** data. Within a SSH Key Pair, //only// the Private Key can decrypt data that has been encrypted with the associated Public Key. | ||
| + | |||
| + | A Private Key should NEVER leave your computer and must stay private. NEVER share it with anyone or send it over the internet in any way. A Public Key on the other hand you can distribute freely. | ||
| + | |||
| + | When you attempt to login to a remote, the remote will take a randomly generated number and encrypt it with the Public Key that is associated with your account. It will then send that encrypted number over the network to your machine and asks you if you can decrypt it. If you can, that means that you are in possession of the associated Private Key, and hence you prove that you are you. | ||
| + | |||
| + | This is more secure compared to the traditional password system because only encrypted data is sent over the network instead of a plain password, and the randomly generated number is different each SSH session. | ||
ssh_keys.1624389147.txt.gz · Last modified: by 134.190.232.18
