![]() Your public key has been saved in /Users/jenny/.ssh/id_ed25519.pub. Your identification has been saved in /Users/jenny/.ssh/id_ed25519. Generating public/private ed25519 key pair.Įnter file in which to save the key (/Users/jenny/.ssh/id_ed25519):Įnter passphrase (empty for no passphrase): The process should complete now and should have looked like this: ~ % ssh-keygen -t ed25519 -C "jenny-2020-mbp" ![]() Enter passphrase (empty for no passphrase): I did not use a passphrase at first, but I do now, and record it in a password manager. If you’re completely new at all this, skip the passphrase and implement it next time, when you are more comfortable with system configuration. It is optional, but also a best practice.Ĭonfiguring your system for smooth operation with a passphrase-protected key introduces more moving parts. You have the option to protect the key with a passphrase. Just press Enter here: Enter file in which to save the key (/Users/jenny/.ssh/id_ed25519): If it appears that your system is too old to support the Ed25519 algorithm, do this instead: ssh-keygen -t rsa -b 4096 -C "DESCRIPTIVE-COMMENT"Īccept the proposal to save the key in the default location. ssh-keygen -t ed25519 -C "DESCRIPTIVE-COMMENT" For example, one public key for each computer you connect with.Ĭreate the key pair like so, but substitute a comment that means something to you, especially if you’ll have multiple SSH keys in your life.Ĭonsider the email associated with your GitHub account or the name of your computer or some combination, e.g.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |