https is easier to use than ssh.
Using ssh, you need to:
- create public / private key
- publish it on github
- running (if you really want security) ssh-agent to enter a passphrase that you would associate with your private key.
https just reuse the GitHub credentials that you already have.
If you do not want to enter a GitHub password for each git command, you can save these credentials in encrypted ~/.netrc.gpg (or %HOME%/_netrc.gpg on the windows).
See A complete step-by-step example in Is there a way to skip password entry when using https: // github ".
I store several credentials (in GitHub, BitBucket, internal repositories, ...) in one (encrypted) file, and I type in one password (gpg passphrase) once in the morning.
I can then access all of these repositories without entering my credentials during the day.
Vonc
source share