this was tested on Linux debian7 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1+deb7u1 x86_64 GNU/Linux
ssh-keys instead of passwords is a saver way of communication/connecting/pushing sources, because it’s not prone to brute-force password-guessing. (believe me i have seen servers with password-auth beeing hacked… )
ssh-keygen -t rsa -C "email@example.com";
chmod 0600 ~/.ssh/id_rsa;
chmod 0700 ~/.ssh/;
# steer your browser to
# and paste what comes out of: (BUT DO NOT COPY THE LINEBREAK!)
# during the step of:
# if you get a message like:
Could not open a connection to your authentication agent.
# do this and try again:
# test connection
ssh -T firstname.lastname@example.org;
The authenticity of host 'github.com (220.127.116.11)' can't be established.
RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'github.com,18.104.22.168' (RSA) to the list of known hosts.
Hi SameUsernameAsOnGithub! You've successfully authenticated, but GitHub does not provide shell access.
We strongly recommend using an SSH connection when interacting with GitHub. SSH keys are a way to identify trusted computers, without involving passwords. The steps below will walk you through generating an SSH key and then adding the public key to your GitHub account.
if you get: "Permission denied (publickey)."
This is a known problem with certain Linux distributions. For a possible resolution, see our help article.