Setup SSH keys for use with GitHub/GitLab/BitBucket etc

README.md

Create a new repository, or reuse an existing one.

Generate a new SSH key:

ssh-keygen -t rsa -C "[email protected]"

Copy the contents of the file ~/.ssh/id_rsa.pub to your SSH keys in your GitHub account settings (https://github.com/settings/keys).

Test SSH key:

$ ssh -T [email protected]
Hi developius! You've successfully authenticated, but GitHub does not provide shell access.

Change directory into the local clone of your repository (if you're not already there) and run:

git remote set-url origin [email protected]:username/your-repository.git

Now try editing a file (try the README) and then do:

$ git commit -am "Update README.md"
$ git push

You should not be asked for a username or password. If it works, your SSH key is correctly configured.

@ajsaraujo @janek done 😄

git remote set-url origin [email protected]:User name /repo.git
this command really works me. thank you.

THX

Easiest way is to use the command line:

Thanks, it worked.

Thanks for the directions. I'm trying this in a shared hosting account. When I try testing the key with ssh -T [email protected] I get:
/bin/sh: /usr/bin/sss_ssh_knownhostsproxy: No such file or directory
ssh_exchange_identification: Connection closed by remote host

Can you help? Is it not possible to set up a SSH key in shared hosting shell?

@argiepiano it looks like your server doesn't have the ssh command configured correctly - you may need to get in touch with your hosting provider as sss_ssh_knownhostsproxy looks like something weird on their end.

Thanks for the guidance but after following the steps it is still asking for the username and password with pushing.

Thanks for the guidance but after following the steps it is still asking for the username and password with pushing.

had the same issue. It helped when I switched to the ssh and not https, Moreover I've added my public-key not to my account settings instead I've added my key to the repo with special rights, I've just created my repo so with a fix new git clone everything was fine but if you had bigger stuff and some branches etc. maybe script this will help https://gist.github.com/m14t/3056747