2017-12-07 7 views
1

私は複数のbitbucketアカウントを持っています。 1つのアカウントには、私がの.ssh/configに次のエントリを持っている第二アカウントのように私はの.ssh/id_rsaと-infoodle二次秘密鍵でビットバスケットにアクセス

を使用したい私の「主」秘密鍵の.ssh/id_rsaとを使用しています。

Host bitbucket.org-infoodle 
    Hostname bitbucket.org 
    User jochen 
    IdentityFile ~/.ssh/id_rsa-bb_infoodle2 
    LogLevel DEBUG3 
コンピュータ1で

が、これは正常に動作します:コンピュータ2オン

[email protected]:~/projects$ git clone [email protected]:richinnz/zog-2017.git clonetest 
Cloning into 'clonetest'... 
debug2: resolving "bitbucket.org" port 22 
debug2: ssh_connect_direct: needpriv 0 
debug1: Connecting to bitbucket.org [104.192.143.1] port 22. 
debug1: Connection established. 
debug1: identity file /home/jochen/.ssh/id_rsa-bb_infoodle2 type 1 
debug1: key_load_public: No such file or directory 
debug1: identity file /home/jochen/.ssh/id_rsa-bb_infoodle2-cert type -1 
debug1: Enabling compatibility mode for protocol 2.0 
debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.2 
debug1: Remote protocol version 2.0, remote software version conker_1.0.315-a08d059 app-165 
debug1: no match: conker_1.0.315-a08d059 app-165 
debug2: fd 3 setting O_NONBLOCK 
debug1: Authenticating to bitbucket.org:22 as 'git' 
debug3: hostkeys_foreach: reading file "/home/jochen/.ssh/known_hosts" 
debug3: record_hostkey: found key type RSA in file /home/jochen/.ssh/known_hosts:241 
debug3: load_hostkeys: loaded 1 keys from bitbucket.org 
debug3: order_hostkeyalgs: prefer hostkeyalgs: [email protected],rsa-sha2-512,rsa-sha2-256,ssh-rsa 
debug3: send packet: type 20 
debug1: SSH2_MSG_KEXINIT sent 
debug3: receive packet: type 20 
debug1: SSH2_MSG_KEXINIT received 
debug2: local client KEXINIT proposal 
debug2: KEX algorithms: [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,ext-info-c 
debug2: host key algorithms: [email protected],rsa-sha2-512,rsa-sha2-256,ssh-rsa,[email protected],[email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519 
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc 
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc 
debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 
debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 
debug2: compression ctos: none,[email protected],zlib 
debug2: compression stoc: none,[email protected],zlib 
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug2: peer server KEXINIT proposal 
debug2: KEX algorithms: [email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 
debug2: host key algorithms: ssh-dss,ssh-rsa 
debug2: ciphers ctos: aes128-ctr,aes192-ctr,aes256-ctr,[email protected],arcfour256,arcfour128 
debug2: ciphers stoc: aes128-ctr,aes192-ctr,aes256-ctr,[email protected],arcfour256,arcfour128 
debug2: MACs ctos: [email protected],hmac-sha2-256,hmac-sha1,hmac-sha1-96 
debug2: MACs stoc: [email protected],hmac-sha2-256,hmac-sha1,hmac-sha1-96 
debug2: compression ctos: none 
debug2: compression stoc: none 
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug1: kex: algorithm: [email protected] 
debug1: kex: host key algorithm: ssh-rsa 
debug1: kex: server->client cipher: aes128-ctr MAC: [email protected] compression: none 
debug1: kex: client->server cipher: aes128-ctr MAC: [email protected] compression: none 
debug3: send packet: type 30 
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY 
debug3: receive packet: type 31 
debug1: Server host key: ssh-rsa SHA256:zzXQOXSRBEiUtuE8AikJYKwbHaxvSc0ojez9YXaGp1A 
debug3: hostkeys_foreach: reading file "/home/jochen/.ssh/known_hosts" 
debug3: record_hostkey: found key type RSA in file /home/jochen/.ssh/known_hosts:241 
debug3: load_hostkeys: loaded 1 keys from bitbucket.org 
debug3: hostkeys_foreach: reading file "/home/jochen/.ssh/known_hosts" 
debug3: record_hostkey: found key type RSA in file /home/jochen/.ssh/known_hosts:242 
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/jochen/.ssh/known_hosts:241 
debug3: send packet: type 21 
debug2: set_newkeys: mode 1 
debug1: rekey after 4294967296 blocks 
debug1: SSH2_MSG_NEWKEYS sent 
debug1: expecting SSH2_MSG_NEWKEYS 
debug3: receive packet: type 21 
debug2: set_newkeys: mode 0 
debug1: rekey after 4294967296 blocks 
debug1: SSH2_MSG_NEWKEYS received 
debug2: key: /home/jochen/.ssh/id_rsa-bb_infoodle2 (0x55f37c38c1c0), explicit, agent 
debug2: key: [email protected] (0x55f37c38d860), agent 
debug2: key: [email protected] (0x55f37c38d8b0), agent 
debug2: key: [email protected] (0x55f37c38f7e0), agent 
debug3: send packet: type 5 
debug3: receive packet: type 6 
debug2: service_accept: ssh-userauth 
debug1: SSH2_MSG_SERVICE_ACCEPT received 
debug3: send packet: type 50 
debug3: receive packet: type 51 
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/jochen/.ssh/id_rsa-bb_infoodle2 
debug3: send_pubkey_test 
debug3: send packet: type 50 
debug2: we sent a publickey packet, wait for reply 
debug3: receive packet: type 60 
debug1: Server accepts key: pkalg ssh-rsa blen 279 
debug2: input_userauth_pk_ok: fp SHA256:gnnMiy+PtixStLXN09+pHjnmcbdVNtgGhc36MOtG4/Y 
debug3: sign_and_send_pubkey: RSA SHA256:gnnMiy+PtixStLXN09+pHjnmcbdVNtgGhc36MOtG4/Y 
debug3: send packet: type 50 
debug3: receive packet: type 52 
debug1: Authentication succeeded (publickey). 
Authenticated to bitbucket.org ([104.192.143.1]:22). 
debug2: fd 5 setting O_NONBLOCK 
debug2: fd 6 setting O_NONBLOCK 
debug1: channel 0: new [client-session] 
debug3: ssh_session2_open: channel_new: 0 
debug2: channel 0: send open 
debug3: send packet: type 90 
debug1: Entering interactive session. 
debug1: pledge: network 
debug3: receive packet: type 91 
debug2: callback start 
debug2: fd 3 setting TCP_NODELAY 
debug3: ssh_packet_set_tos: set IP_TOS 0x08 
debug2: client_session2_setup: id 0 
debug1: Sending environment. 
debug3: Ignored env XDG_VTNR 
debug3: Ignored env XDG_SESSION_ID 
debug3: Ignored env XDG_GREETER_DATA_DIR 
debug3: Ignored env CLUTTER_IM_MODULE 
debug3: Ignored env QT_STYLE_OVERRIDE 
debug3: Ignored env SESSION 
debug3: Ignored env GPG_AGENT_INFO 
debug3: Ignored env GLADE_PIXMAP_PATH 
debug3: Ignored env TERM 
debug3: Ignored env XDG_MENU_PREFIX 
debug3: Ignored env SHELL 
debug3: Ignored env QT_LINUX_ACCESSIBILITY_ALWAYS_ON 
debug3: Ignored env WINDOWID 
debug3: Ignored env UPSTART_SESSION 
debug3: Ignored env GNOME_KEYRING_CONTROL 
debug3: Ignored env GTK_MODULES 
debug3: Ignored env ANSIBLE_HOSTS 
debug3: Ignored env USER 
debug3: Ignored env LS_COLORS 
debug3: Ignored env CLUTTER_BACKEND 
debug3: Ignored env QT_ACCESSIBILITY 
debug3: Ignored env XDG_SESSION_PATH 
debug3: Ignored env GLADE_MODULE_PATH 
debug3: Ignored env XDG_SEAT_PATH 
debug3: Ignored env SSH_AUTH_SOCK 
debug3: Ignored env DEFAULTS_PATH 
debug3: Ignored env SESSION_MANAGER 
debug3: Ignored env XDG_CONFIG_DIRS 
debug3: Ignored env DESKTOP_SESSION 
debug3: Ignored env PATH 
debug3: Ignored env QT_IM_MODULE 
debug3: Ignored env QT_QPA_PLATFORMTHEME 
debug3: Ignored env XDG_SESSION_TYPE 
debug3: Ignored env PWD 
debug3: Ignored env JOB 
debug3: Ignored env XMODIFIERS 
debug3: Ignored env GNOME_KEYRING_PID 
debug1: Sending env LANG = en_NZ.UTF-8 
debug2: channel 0: request env confirm 0 
debug3: send packet: type 98 
debug3: Ignored env GDM_LANG 
debug3: Ignored env MANDATORY_PATH 
debug3: Ignored env IM_CONFIG_PHASE 
debug3: Ignored env GDMSESSION 
debug3: Ignored env HISTCONTROL 
debug3: Ignored env SESSIONTYPE 
debug3: Ignored env GTK2_MODULES 
debug3: Ignored env SPEECHD_PORT 
debug3: Ignored env SHLVL 
debug3: Ignored env HOME 
debug3: Ignored env XDG_SEAT 
debug3: Ignored env LANGUAGE 
debug3: Ignored env UPSTART_INSTANCE 
debug3: Ignored env GTK_OVERLAY_SCROLLING 
debug3: Ignored env UPSTART_EVENTS 
debug3: Ignored env XDG_SESSION_DESKTOP 
debug3: Ignored env LOGNAME 
debug3: Ignored env DBUS_SESSION_BUS_ADDRESS 
debug3: Ignored env XDG_DATA_DIRS 
debug3: Ignored env QT4_IM_MODULE 
debug3: Ignored env LESSOPEN 
debug3: Ignored env INSTANCE 
debug3: Ignored env UPSTART_JOB 
debug3: Ignored env XDG_RUNTIME_DIR 
debug3: Ignored env DISPLAY 
debug3: Ignored env GLADE_CATALOG_PATH 
debug3: Ignored env XDG_CURRENT_DESKTOP 
debug3: Ignored env GTK_IM_MODULE 
debug3: Ignored env LESSCLOSE 
debug3: Ignored env XAUTHORITY 
debug3: Ignored env COLORTERM 
debug3: Ignored env OLDPWD 
debug3: Ignored env _ 
debug1: Sending command: git-upload-pack 'richinnz/zog-2017.git' 
debug2: channel 0: request exec confirm 1 
debug3: send packet: type 98 
debug2: callback done 
debug2: channel 0: open confirm rwindow 2097152 rmax 32768 
debug3: receive packet: type 99 
debug2: channel_input_status_confirm: type 99 id 0 
debug2: exec request accepted on channel 0 
debug2: channel 0: rcvd adjust 4532 
remote: Counting objects: 14510, done. 
^Cdebug3: send packet: type 1 23% (1424/6189) 
debug1: channel 0: free: client-session, nchannels 1 
debug3: channel 0: status: The following connections are open: 
    #0 client-session (t4 r0 i0/0 o0/0 fd 5/6 cc -1) 

debug1: fd 0 clearing O_NONBLOCK 
debug1: fd 1 clearing O_NONBLOCK 
debug1: Killed by signal 2. 
fatal: The remote end hung up unexpectedly 

は、しかし、それは

[email protected]:~/projects$ git clone [email protected]:richinnz/zog-2017.git zog 
Cloning into 'zog'... 
debug2: resolving "bitbucket.org" port 22 
debug2: ssh_connect_direct: needpriv 0 
debug1: Connecting to bitbucket.org [104.192.143.2] port 22. 
debug1: Connection established. 
debug1: identity file /home/jochen/.ssh/id_rsa-bb_infoodle2 type 1 
debug1: key_load_public: No such file or directory 
debug1: identity file /home/jochen/.ssh/id_rsa-bb_infoodle2-cert type -1 
debug1: Enabling compatibility mode for protocol 2.0 
debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.2 
debug1: Remote protocol version 2.0, remote software version conker_1.0.315-a08d059 app-129 
debug1: no match: conker_1.0.315-a08d059 app-129 
debug2: fd 3 setting O_NONBLOCK 
debug1: Authenticating to bitbucket.org:22 as 'git' 
debug3: hostkeys_foreach: reading file "/home/jochen/.ssh/known_hosts" 
debug3: record_hostkey: found key type RSA in file /home/jochen/.ssh/known_hosts:22 
debug3: load_hostkeys: loaded 1 keys from bitbucket.org 
debug3: order_hostkeyalgs: prefer hostkeyalgs: [email protected],rsa-sha2-512,rsa-sha2-256,ssh-rsa 
debug3: send packet: type 20 
debug1: SSH2_MSG_KEXINIT sent 
debug3: receive packet: type 20 
debug1: SSH2_MSG_KEXINIT received 
debug2: local client KEXINIT proposal 
debug2: KEX algorithms: [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,ext-info-c 
debug2: host key algorithms: [email protected],rsa-sha2-512,rsa-sha2-256,ssh-rsa,[email protected],[email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519 
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc 
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc 
debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 
debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 
debug2: compression ctos: none,[email protected],zlib 
debug2: compression stoc: none,[email protected],zlib 
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug2: peer server KEXINIT proposal 
debug2: KEX algorithms: [email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 
debug2: host key algorithms: ssh-dss,ssh-rsa 
debug2: ciphers ctos: aes128-ctr,aes192-ctr,aes256-ctr,[email protected],arcfour256,arcfour128 
debug2: ciphers stoc: aes128-ctr,aes192-ctr,aes256-ctr,[email protected],arcfour256,arcfour128 
debug2: MACs ctos: [email protected],hmac-sha2-256,hmac-sha1,hmac-sha1-96 
debug2: MACs stoc: [email protected],hmac-sha2-256,hmac-sha1,hmac-sha1-96 
debug2: compression ctos: none 
debug2: compression stoc: none 
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug1: kex: algorithm: [email protected] 
debug1: kex: host key algorithm: ssh-rsa 
debug1: kex: server->client cipher: aes128-ctr MAC: [email protected] compression: none 
debug1: kex: client->server cipher: aes128-ctr MAC: [email protected] compression: none 
debug3: send packet: type 30 
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY 
debug3: receive packet: type 31 
debug1: Server host key: ssh-rsa SHA256:zzXQOXSRBEiUtuE8AikJYKwbHaxvSc0ojez9YXaGp1A 
debug3: hostkeys_foreach: reading file "/home/jochen/.ssh/known_hosts" 
debug3: record_hostkey: found key type RSA in file /home/jochen/.ssh/known_hosts:22 
debug3: load_hostkeys: loaded 1 keys from bitbucket.org 
debug3: hostkeys_foreach: reading file "/home/jochen/.ssh/known_hosts" 
debug3: record_hostkey: found key type RSA in file /home/jochen/.ssh/known_hosts:23 
debug3: load_hostkeys: loaded 1 keys from 104.192.143.2 
debug1: Host 'bitbucket.org' is known and matches the RSA host key. 
debug1: Found key in /home/jochen/.ssh/known_hosts:22 
debug3: send packet: type 21 
debug2: set_newkeys: mode 1 
debug1: rekey after 4294967296 blocks 
debug1: SSH2_MSG_NEWKEYS sent 
debug1: expecting SSH2_MSG_NEWKEYS 
debug3: receive packet: type 21 
debug2: set_newkeys: mode 0 
debug1: rekey after 4294967296 blocks 
debug1: SSH2_MSG_NEWKEYS received 
debug2: key: jochen-windows (0x55c4e8b8f3a0), agent 
debug2: key: /home/jochen/.ssh/id_rsa-bb_infoodle2 (0x55c4e8b8f2d0), explicit 
debug3: send packet: type 5 
debug3: receive packet: type 6 
debug2: service_accept: ssh-userauth 
debug1: SSH2_MSG_SERVICE_ACCEPT received 
debug3: send packet: type 50 
debug3: receive packet: type 51 
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: jochen-windows 
debug3: send_pubkey_test 
debug3: send packet: type 50 
debug2: we sent a publickey packet, wait for reply 
debug3: receive packet: type 60 
debug1: Server accepts key: pkalg ssh-rsa blen 277 
debug2: input_userauth_pk_ok: fp SHA256:JiGG4lMVcyq8MOzTMskuOZ7ww6maX6wjpMVjW76t9+Q 
debug3: sign_and_send_pubkey: RSA SHA256:JiGG4lMVcyq8MOzTMskuOZ7ww6maX6wjpMVjW76t9+Q 
debug3: send packet: type 50 
debug3: receive packet: type 52 
debug1: Authentication succeeded (publickey). 
Authenticated to bitbucket.org ([104.192.143.2]:22). 
debug2: fd 5 setting O_NONBLOCK 
debug2: fd 6 setting O_NONBLOCK 
debug1: channel 0: new [client-session] 
debug3: ssh_session2_open: channel_new: 0 
debug2: channel 0: send open 
debug3: send packet: type 90 
debug1: Entering interactive session. 
debug1: pledge: network 
debug3: receive packet: type 91 
debug2: callback start 
debug2: fd 3 setting TCP_NODELAY 
debug3: ssh_packet_set_tos: set IP_TOS 0x08 
debug2: client_session2_setup: id 0 
debug1: Sending environment. 
debug3: Ignored env XDG_SESSION_ID 
debug3: Ignored env TERM 
debug3: Ignored env SHELL 
debug3: Ignored env SSH_CLIENT 
debug3: Ignored env SSH_TTY 
debug3: Ignored env USER 
debug3: Ignored env LS_COLORS 
debug3: Ignored env SSH_AUTH_SOCK 
debug3: Ignored env MAIL 
debug3: Ignored env PATH 
debug3: Ignored env PWD 
debug1: Sending env LANG = en_US.UTF-8 
debug2: channel 0: request env confirm 0 
debug3: send packet: type 98 
debug3: Ignored env SHLVL 
debug3: Ignored env HOME 
debug3: Ignored env LOGNAME 
debug3: Ignored env SSH_CONNECTION 
debug3: Ignored env LESSOPEN 
debug3: Ignored env XDG_RUNTIME_DIR 
debug3: Ignored env DISPLAY 
debug3: Ignored env LESSCLOSE 
debug3: Ignored env _ 
debug3: Ignored env OLDPWD 
debug1: Sending command: git-upload-pack 'richinnz/zog-2017.git' 
debug2: channel 0: request exec confirm 1 
debug3: send packet: type 98 
debug2: callback done 
debug2: channel 0: open confirm rwindow 2097152 rmax 32768 
debug3: receive packet: type 99 
debug2: channel_input_status_confirm: type 99 id 0 
debug2: exec request accepted on channel 0 
debug2: channel 0: rcvd ext data 26 
debug3: receive packet: type 98 
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 
debug3: receive packet: type 96 
debug2: channel 0: rcvd eof 
debug2: channel 0: output open -> drain 
debug3: receive packet: type 97 
debug2: channel 0: rcvd close 
debug2: channel 0: close_read 
debug2: channel 0: input open -> closed 
debug3: channel 0: will not send data after close 
debug2: channel 0: obuf_empty delayed efd 7/(26) 
repository access denied. 
debug2: channel 0: written 26 to efd 7 
debug3: channel 0: will not send data after close 
debug2: channel 0: obuf empty 
debug2: channel 0: close_write 
debug2: channel 0: output drain -> closed 
debug2: channel 0: almost dead 
debug2: channel 0: gc: notify user 
debug2: channel 0: gc: user detached 
debug2: channel 0: send close 
debug3: send packet: type 97 
debug2: channel 0: is dead 
debug2: channel 0: garbage collecting 
debug1: channel 0: free: client-session, nchannels 1 
debug3: channel 0: status: The following connections are open: 
    #0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cc -1) 

debug3: send packet: type 1 
debug1: fd 0 clearing O_NONBLOCK 
debug1: fd 1 clearing O_NONBLOCK 
Transferred: sent 2700, received 1736 bytes, in 0.5 seconds 
Bytes per second: sent 5293.0, received 3403.2 
debug1: Exit status 1 
fatal: Could not read from remote repository. 

Please make sure you have the correct access rights 
and the repository exists. 

両方コンプを失敗しますコンピュータ1は、ニュージーランドに位置しているのUbuntu 16.04、uterは、コンピュータ2は、AWSシドニーで

に位置している私が試してみました:

  • をコンピュータ1と同じにコンピュータ2のbitbucket.orgのIPアドレスを設定(中/ .sshからの.ssh/id_rsaとの除去etc/hostsファイル)
  • /間違った秘密鍵は
  • は、彼らがしていることを確認するコンピュータ2新しいキーにコンピュータ1から
  • コピーの.ssh/configに作成ピックアップされていないことを確認することが同じ

これを解決する他に何ができますか?

答えて

1

Bitbucketの場合、.ssh/configファイルでUser gitを使用する必要があります。

なしUser xxx

Host bitbucket.org-infoodle 
    Hostname bitbucket.org 
    User git         <============ 
    IdentityFile ~/.ssh/id_rsa-bb_infoodle2 
    LogLevel DEBUG3 

BitBucketは、そのユーザーのリモートssh接続のみを受け入れます。
そして、あなたを認証するために公開鍵を使用します。

そして、あなたは[email protected]を必要としないが、ちょうどbitbucket.org-infoodle:...

は "Why does Git using ssh use git as a username" を参照してください。

実際の問題は、ネットワークの品質に関連するようですが、ssh設定には関係していないようです。


私はsudoのgitの設定--system --unset credential.helper

I describe that hereと私の資格情報をクリアすると信じていますが、これはHTTPSのURLではなく、SSHのものです。
リモコン:git remote -vを再確認してください。

+0

あなたが少なくとも 'ssh -T bitbucket.org-infoodle'で認証されているかどうかをテストしてください。 – VonC

+0

はい私は認証されましたが、間違ったユーザです。 .sshからすべての秘密鍵を削除しても、私はまだ認証されています。私はクレデンシャルキャッシュとユーザの.git /フォルダをクリアしてみましたが、何も見つかりませんでした。私はリポジトリフォルダにいません – jdog

+0

メインのbitbucketユーザから公開鍵を削除してこのリポジトリをクローンするために接続することができました。しかし私はまだどこに鍵が保存されているのか分からない – jdog