All geek questions in one place

GitHub permission denial (public key)

I get the following listing with the -vT (as per github troubleshooting)

 OpenSSH_5.6p1, OpenSSL 0.9.8r 8 Feb 2011 debug1: Reading configuration data /Users/someuser/.ssh/config debug1: Applying options for github.com debug1: Reading configuration data /etc/ssh_config debug1: Applying options for * debug1: Connecting to github.com [207.97.227.239] port 22. debug1: Connection established. debug1: identity file /Users/someuser/.ssh/github_rsa type 1 debug1: identity file /Users/someuser/.ssh/github_rsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian-5github2 debug1: match: OpenSSH_5.1p1 Debian-5github2 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.6 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5 none debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'github.com' is known and matches the RSA host key. debug1: Found key in /Users/someuser/.ssh/known_hosts:2 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/someuser/.ssh/github_rsa debug1: Authentications that can continue: publickey debug1: No more authentication methods to try. Permission denied (publickey).

It worked correctly as of yesterday. Since then I restarted the computer and now I have a different network. However, it seems that the network is not a problem, since I am establishing a connection through port 22.

Does anyone have any ideas?

+4
source share
1 answer

This question is a bit outdated, but I ran into the same problem and ended up getting a job for myself, so I thought I was offering something that worked for me here.

When you clone, make sure you are not using the http URL.

Do it:

 git clone git@github.com :foo/project-name.git

Not this:

 git clone http://github.com/foo/project-name

I originally cloned an http URL that did not allow my ssh credentials to be affected. I'm not sure if this is your problem as you said it works the day before, but it might give you something to try.

FYI - to get the url of the current repo you checked, do the following:

 cd $REPO_DIR git config --list | grep remote.origin.url
+1
source

Source: https://habr.com/ru/post/1385965/

More articles:


All Articles