Ssh-agent is a program that starts when you log in and stores your private keys. You can read more about how SSH / RSA key pairs work here. It's extremely important that you never reveal your private key, and only use your public key for things like GitHub authentication.
Note: SSH keys are always generated as a pair of public ( id_rsa.pub) and private ( id_rsa) keys. Then generate a new set of keys with: ssh-keygen -t rsa -b 4096 -C check that your keys exist with the ls -al ~/.ssh command and ensure that the output is similar to the one listed above. If you don't see any output or that directory doesn't exist (you get a No such file or directory message), then run: mkdir $HOME/.ssh If your keys already exist, skip ahead to the Copy your public SSH key section below. rw- 1 user_name user_name 12892 Feb 5 18:39 known_hosts rw-r-r- 1 user_name user_name 414 id_rsa.pub If you've already generated SSH keys, you should see output similar to this: -rw- 1 user_name user_name 1766 id_rsa Open a terminal and enter the following command: ls -al ~/.ssh
Check for an existing SSH keyįirst, check if you've already generated SSH keys for your machine. Here's a quick guide to generate and configure an SSH key with GitHub so you never have to authenticate the old fashioned way again. Just think–all of that time you spent entering your email address and password into the console every time you push a commit could have been spent coding. If you use GitHub without setting up an SSH key, you're really missing out.
0 kommentar(er)
