[P03] Caveats for using SSH with Github

One of the most convenient way of working in Ubuntu is SSH! It’s not included in Windows by default and working with SSH require 3rd party software (e.g. putty). But when I’ve migrated from windows and working on Github in Ubuntu, it perfectly make sense to SSH for push-pull purpose so that I don’t have to give my username and password everytime. In this post, writing some caveats I found while working with SSH for Github.

List:

  1. The repository must be cloned via ssh, not https.
  2. I had saved my passpharse in system. However, if it’s not intended (password freak like me), then guideline here to undo this: https://apple.stackexchange.com/a/142541
  3. If you maintain multiple SSH key in Github, it is important to identify each SSH public key individually. Initially I deleted wrong key and had problem from Ubuntu. Afterwards, I followed same convention for server naming to name my SSH public keys, and there were no problems.
  4. In order to copy the public key, most of the articles will suggest to use `xclip` but I just used `cat ~/.ssh/id_rsa.pub` and copy-pasted the code from terminal.
  5. I think that the email of Github should match with the email of the SSH key. But didn’t test this yet.

Helpful youtube video:

Leave a Reply

Your email address will not be published. Required fields are marked *