-
Bug
-
Resolution: Fixed
-
Medium
Hi,
I have a problem when trying to commit. It always asks for a password even though I have the key correctly configured.
I tried to log in with ssh and this happened:
#!bash OpenSSH_5.9p1, OpenSSL 0.9.8y 5 Feb 2013 debug1: Reading configuration data /etc/ssh_config debug1: /etc/ssh_config line 20: Applying options for * debug1: /etc/ssh_config line 53: Applying options for * debug1: Connecting to bitbucket.org [131.103.20.168] port 22. debug1: Connection established. debug1: identity file /Users/<edited out>/.ssh/id_rsa type 1 debug1: identity file /Users/<edited out>/.ssh/id_rsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.9 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: Server host key: RSA 97:8c:1b:f2:6f:14:6b:5c:3b:ec:aa:46:46:74:7c:40 debug1: Host 'bitbucket.org' is known and matches the RSA host key. debug1: Found key in /Users/<edited out>/.ssh/known_hosts:1 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/<edited out>/.ssh/id_rsa debug1: Authentications that can continue: publickey debug1: Offering RSA public key: /Users/<edited out>/.ssh/id_rsa debug1: Authentications that can continue: publickey debug1: No more authentication methods to try. Permission denied (publickey).
I have tried to add my public key to the authorized_keys file in another machine and I could connect without issues, so I am confident the problem is not on my side, but maybe I am wrong.
Either way I don't know what else to try.
Thank you very much for your time.
[BCLOUD-8330] Problem with ssh key
Pretty stupid mistake actually. When I was connecting via git it was through https hence why it didn't work. And when I was doing so via ssh I was using my own username instead of git.
So, you can delete this, and sorry about it.
Pretty stupid mistake actually. When I was connecting via git it was through https hence why it didn't work. And when I was doing so via ssh I was using my own username instead of git.
So, you can delete this, and sorry about it.