Geek Answers Handbook

$ ssh -T git @github - permission is allowed (public key)

I am the first GitHub user. I installed Git for Windows following the instructions: http://help.github.com/win-set-up-git/

Came to the point of generating a public ssh key. Git Bash is open. Generated a key, saved it on github.com in my SSH public keys, now I tried access to ssh:

$ ssh -T git@github.com Permission denied (publickey).

What happened? The instructions say that everything should go well. Maybe I need to reboot or wait for the github.com server to recognize my key?

Please, help.

Thanks in advance!

+4
source share
6 answers

Had to use exec ssh-agent bash . That helped:

 $ exec ssh-agent bash bash-3.1$ ssh-add f:/GIT/.ssh/id_rsa Enter passphrase for f:/GIT/.ssh/id_rsa: Identity added: f:/GIT/.ssh/id_rsa (f:/GIT/.ssh/id_rsa) bash-3.1$ ssh git@github.com Hi MichaelZelensky! You've successfully authenticated, but GitHub does not provi de shell access. Connection to github.com closed.
+3
source 
  ssh-keygen -t rsa copy the key generated in the file ~/.ssh/id_rsa.pub (open with notepad) paste this key in the "add ssh key" section of your github account
+4
source

I had the same problem. Although each instruction was followed; The public key is genereated and added to my Github account, I continued to get the error ... Until I restarted my machine. I suggest you do the same. Hope this should fix this.

+3
source

For me (windows xp, a reasonably new installation) when generating ssh keys via mingw32, the .ssh directory did not exist, that I saved the keys.

Instead of creating ssh-keygen, they were placed in the root of the user directory (C: \ Documents and Settings \).

This gave a permission denial error (public key).

A simple solution...

Move the key files to the .ssh directory! (by the way, this seemed to be created when I said yes to continue connecting after the authenticity of the host .... message)

+2
source

I had the same problem, I generated my ssh-keygen after I added my public key to GitHub and they told me the same problem, but what you need gives permission to the .ssh folder, I I solve this problem, I know how to do it, but I was growing, but check it out, maybe this is the same solution.

 sudo chmod 777 -R .ssh
-1
source

More articles:


All Articles