2016-06-09 8 views
0

Я выполнил инструкции, приведенные в этом Atlassian Documentation, для нескольких идентификаторов ssh.~/.ssh/config не работает для нескольких идентификаторов в учетной записи bitbucket?

Вот тождества, как указано:

$ ssh-add -l 
4096 SHA256:bWBUbxKV4xJ5aOwrcshlfq6qMq6upXmphMkgYONwApU bitbucket:[email protected] (RSA) 
4096 SHA256:gzM1ZEJPi8Ke3i3Ny1azl/ytqOHOd0AiP1hRgn58tBw github:[email protected] (RSA) 
4096 SHA256:555uTqY8ijI7Jj8cyBeTkh6zGcDrFO+Kf7p9XLIPd64 bitbucket:[email protected] (RSA) 
4096 SHA256:LGS5XTYu/nxtaa69JO0SZ1sUt6M1do6YCJSDdGpOVtA gitlab:[email protected] (RSA) 

Вот ~/ssh./config:

Host bitbucket-foo1 
    HostName bitbucket.org 
    IdentityFile ~/.ssh/id_rsa_bitbucket 

Host github-foo2 
    HostName github.com 
    IdentityFile ~/.ssh/id_rsa_github 

Host bitbucket-foo3 
    HostName bitbucket.org 
    IdentityFile ~/.ssh/id_rsa_legalmatch 

Host gitlab-foo4 
    HostName gitlab.com 
    IdentityFile ~/.ssh/id_rsa_gitlab 

Проблема сейчас в том, что bitbucket-foo3 не пройти аутентификацию. bitbucket-foo1, а остальное отлично работает.

Я пытался использовать ssh -vvv [email protected], вот лог:

$ ssh -vvv [email protected] 
OpenSSH_6.9p1 Ubuntu-2ubuntu0.2, OpenSSL 1.0.2d 9 Jul 2015 
debug1: Reading configuration data /home/ryeballar/.ssh/config 
debug1: /home/ryeballar/.ssh/config line 13: Applying options for bitbucket-foo3 
debug1: Reading configuration data /etc/ssh/ssh_config 
debug1: /etc/ssh/ssh_config line 19: Applying options for * 
debug2: ssh_connect: needpriv 0 
debug1: Connecting to bitbucket.org [104.192.143.1] port 22. 
debug1: Connection established. 
debug1: identity file /home/ryeballar/.ssh/id_rsa_legalmatch type 1 
debug1: key_load_public: No such file or directory 
debug1: identity file /home/ryeballar/.ssh/id_rsa_legalmatch-cert type -1 
debug1: Enabling compatibility mode for protocol 2.0 
debug1: Local version string SSH-2.0-OpenSSH_6.9p1 Ubuntu-2ubuntu0.2 
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.4 
debug1: match: OpenSSH_6.4 pat OpenSSH* compat 0x04000000 
debug2: fd 3 setting O_NONBLOCK 
debug1: Authenticating to bitbucket.org:22 as 'user' 
debug3: hostkeys_foreach: reading file "/home/ryeballar/.ssh/known_hosts" 
debug3: record_hostkey: found key type RSA in file /home/ryeballar/.ssh/known_hosts:4 
debug3: load_hostkeys: loaded 1 keys from bitbucket.org 
debug3: order_hostkeyalgs: prefer hostkeyalgs: [email protected],[email protected],ssh-rsa 
debug1: SSH2_MSG_KEXINIT sent 
debug1: SSH2_MSG_KEXINIT received 
debug2: kex_parse_kexinit: [email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 
debug2: kex_parse_kexinit: [email protected],[email protected],ssh-rsa,[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,ssh-dss 
debug2: kex_parse_kexinit: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,[email protected] 
debug2: kex_parse_kexinit: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,[email protected] 
debug2: kex_parse_kexinit: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1,[email protected],[email protected],[email protected],[email protected],hmac-md5,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 
debug2: kex_parse_kexinit: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1,[email protected],[email protected],[email protected],[email protected],hmac-md5,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 
debug2: kex_parse_kexinit: none,[email protected],zlib 
debug2: kex_parse_kexinit: none,[email protected],zlib 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: kex_parse_kexinit: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 
debug2: kex_parse_kexinit: ssh-dss,ssh-rsa 
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,[email protected],[email protected],aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,[email protected] 
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,[email protected],[email protected],aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,[email protected] 
debug2: kex_parse_kexinit: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-md5,hmac-sha1,[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 
debug2: kex_parse_kexinit: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-md5,hmac-sha1,[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 
debug2: kex_parse_kexinit: none,[email protected] 
debug2: kex_parse_kexinit: none,[email protected] 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug1: kex: server->client aes128-ctr [email protected] none 
debug1: kex: client->server aes128-ctr [email protected] none 
debug1: sending SSH2_MSG_KEX_ECDH_INIT 
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY 
debug1: Server host key: ssh-rsa SHA256:zzXQOXSRBEiUtuE8AikJYKwbHaxvSc0ojez9YXaGp1A 
debug3: hostkeys_foreach: reading file "/home/ryeballar/.ssh/known_hosts" 
debug3: record_hostkey: found key type RSA in file /home/ryeballar/.ssh/known_hosts:4 
debug3: load_hostkeys: loaded 1 keys from bitbucket.org 
debug3: hostkeys_foreach: reading file "/home/ryeballar/.ssh/known_hosts" 
debug3: record_hostkey: found key type RSA in file /home/ryeballar/.ssh/known_hosts:5 
debug3: load_hostkeys: loaded 1 keys from 104.192.143.1 
debug1: Host 'bitbucket.org' is known and matches the RSA host key. 
debug1: Found key in /home/ryeballar/.ssh/known_hosts:4 
debug2: set_newkeys: mode 1 
debug1: SSH2_MSG_NEWKEYS sent 
debug1: expecting SSH2_MSG_NEWKEYS 
debug2: set_newkeys: mode 0 
debug1: SSH2_MSG_NEWKEYS received 
debug1: SSH2_MSG_SERVICE_REQUEST sent 
debug2: service_accept: ssh-userauth 
debug1: SSH2_MSG_SERVICE_ACCEPT received 
debug2: key: /home/ryeballar/.ssh/id_rsa_legalmatch (0x55c8f9da84c0), explicit 
debug2: key: bitbucket:[email protected] (0x55c8f9da8d60), 
debug2: key: github:[email protected] (0x55c8f9da82a0), 
debug2: key: gitlab:[email protected] (0x55c8f9dab900), 
debug1: Authentications that can continue: publickey 
debug3: start over, passed a different list publickey 
debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password 
debug3: authmethod_lookup publickey 
debug3: remaining preferred: keyboard-interactive,password 
debug3: authmethod_is_enabled publickey 
debug1: Next authentication method: publickey 
debug1: Offering RSA public key: /home/ryeballar/.ssh/id_rsa_legalmatch 
debug3: send_pubkey_test 
debug2: we sent a publickey packet, wait for reply 
debug1: Authentications that can continue: publickey 
debug1: Offering RSA public key: bitbucket:[email protected] 
debug3: send_pubkey_test 
debug2: we sent a publickey packet, wait for reply 
debug1: Authentications that can continue: publickey 
debug1: Offering RSA public key: github:[email protected] 
debug3: send_pubkey_test 
debug2: we sent a publickey packet, wait for reply 
debug1: Authentications that can continue: publickey 
debug1: Offering RSA public key: gitlab:[email protected] 
debug3: send_pubkey_test 
debug2: we sent a publickey packet, wait for reply 
debug1: Authentications that can continue: publickey 
debug2: we did not send a packet, disable method 
debug1: No more authentication methods to try. 
Permission denied (publickey). 
+0

Как ssh знать, использовать ключ 3 вместо ключа 1? Оба имеют одинаковое имя хоста 'bitbucket.org'. – xxfelixxx

+0

@xxfelixxx 'HostName' указывает реальное имя хоста для входа в систему. И если вы читаете [Atlassian Documentation] (https://confluence.atlassian.com/bitbucket/configure-multiple-ssh-identities-for-gitbash-mac-osx-linux-271943168.html#ConfiguremultipleSSHidentities дляGitBash, MacOSX ,&Linux- CreateaSSHconfigfile), вот как они структурировали его. – ryeballar

+0

@xxfelixxx Я также попытался изменить его, но я думаю, что нет смысла его менять. Несмотря на это, это не сработало. – ryeballar

ответ

0

Кажется, что все, что мне нужно сделать, это просто изменить Bitbucket хоста, используя псевдоним в удаленном origin. Проблема заключалась в том, что старый ключ ssh больше не распознавался, поскольку он использует новый, который был добавлен.

Так изменение дистанционного origin от:

[email protected]:<project-url>.git 

в

[email protected]:<project-url>.git 

решить эту проблему для меня.