38,760
edits
Securing your account/en: Difference between revisions
Jump to navigation
Jump to search
Updating to match new version of source page
(Updating to match new version of source page) |
(Updating to match new version of source page) Tags: Mobile edit Mobile web edit |
||
| Line 2: | Line 2: | ||
= Authentication = | = Authentication = | ||
There are two primary authentication mechanisms that are used to connect to a cluster : passwords and SSH keys. Below are some best practices for both methods. | There are two primary authentication mechanisms that are used to connect to a cluster: passwords and SSH keys. Below are some best practices for both methods. | ||
== Password best practices == | == Password best practices == | ||
| Line 14: | Line 14: | ||
== SSH keys best practices == | == SSH keys best practices == | ||
SSH keys can be a good way to authenticate to your account without typing your password every time. However, to be secure, it is '''imperative that SSH keys use a strong passphrase''' that is treated like a password. | SSH keys can be a good way to authenticate to your account without typing your password every time. However, to be secure, it is '''imperative that SSH keys use a strong passphrase''' that is treated like a password. | ||
Treat the private key as a security token, even when encrypted with a passphrase. Avoid putting a private key on any shared machine. Placing an unencrypted private key on the clusters is a huge security hole. | |||
For technical details on implementing SSH keys for your account, please see [[SSH_Keys|this page]]. | For technical details on implementing SSH keys for your account, please see [[SSH_Keys|this page]]. | ||