{"thread":{"id":"56736","subject":"Git failed to pull after upgrading to 2.33.1, using choco","startedAt":"2021-10-19T02:34:06Z","lastAt":"2021-10-19T23:20:34Z","messageCount":4,"participants":["LL L","Bryan Turner","brian m. carlson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"439011","messageId":"001401d7c490$e7d57620$b7806260$@xeltek-cn.com","threadId":"56736","inReplyTo":null,"subject":"Git failed to pull after upgrading to 2.33.1, using choco","fromName":"LL L","fromEmail":"lll@xeltek-cn.com","sentAt":"2021-10-19T02:27:43Z","receivedAt":"2021-10-19T02:34:06Z","isPatch":false,"sender":{"key":"lll@xeltek-cn.com","avatar":null},"body":"Thank you for filling out a Git bug report!\nPlease answer the following questions to help us understand your issue.\n\nWhat did you do before the bug happened? (Steps to reproduce your issue)\n\n1. uninstall git for windows 2.32.2\n2. install git again with： choco install -y git\n3. git pull emit error:\n\ngit@e.coding.net: Permission denied (publickey).\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n\n4. I am sure it is caused by the upgrading, I observed same issue on my other windows 10 machine..\n\nWhat did you expect to happen? (Expected behavior)\n\npull from origin;\n\nWhat happened instead? (Actual behavior)\n\ngit@e.coding.net: Permission denied (publickey).\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n\nWhat's different between what you expected and what actually happened?\n\nIt doesn't work.\n\nAnything else you want to add:\n\ncoding:/mytex on  trunk [?]\n❯ git pull\ngit@e.coding.net: Permission denied (publickey).\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n\ncoding:/mytex on  trunk [?] took 13s\n❯ ssh -Tv git@e.coding.net\nOpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2\ndebug1: Reading configuration data C:\\\\Users\\\\LL L/.ssh/config\ndebug1: Connecting to e.coding.net [81.69.155.167] port 22.\ndebug1: Connection established.\ndebug1: identity file C:\\\\Users\\\\LL L/.ssh/id_rsa type 0\ndebug1: identity file C:\\\\Users\\\\LL L/.ssh/id_rsa-cert type -1\ndebug1: identity file C:\\\\Users\\\\LL L/.ssh/id_dsa type -1\ndebug1: identity file C:\\\\Users\\\\LL L/.ssh/id_dsa-cert type -1\ndebug1: identity file C:\\\\Users\\\\LL L/.ssh/id_ecdsa type -1\ndebug1: identity file C:\\\\Users\\\\LL L/.ssh/id_ecdsa-cert type -1\ndebug1: identity file C:\\\\Users\\\\LL L/.ssh/id_ed25519 type -1\ndebug1: identity file C:\\\\Users\\\\LL L/.ssh/id_ed25519-cert type -1\ndebug1: identity file C:\\\\Users\\\\LL L/.ssh/id_xmss type -1\ndebug1: identity file C:\\\\Users\\\\LL L/.ssh/id_xmss-cert type -1\ndebug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.1\ndebug1: Remote protocol version 2.0, remote software version Go-CodingGit\ndebug1: no match: Go-CodingGit\ndebug1: Authenticating to e.coding.net:22 as 'git'\ndebug1: SSH2_MSG_KEXINIT sent\ndebug1: SSH2_MSG_KEXINIT received\ndebug1: kex: algorithm: curve25519-sha256@libssh.org\ndebug1: kex: host key algorithm: rsa-sha2-512\ndebug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: compression: none\ndebug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: compression: none\ndebug1: expecting SSH2_MSG_KEX_ECDH_REPLY\ndebug1: Server host key: ssh-rsa SHA256:jok3FH7q5LJ6qvE7iPNehBgXRw51ErE77S0Dn+Vg/Ik\ndebug1: Host 'e.coding.net' is known and matches the RSA host key.\ndebug1: Found key in C:\\\\Users\\\\LL L/.ssh/known_hosts:28\ndebug1: rekey out after 134217728 blocks\ndebug1: SSH2_MSG_NEWKEYS sent\ndebug1: expecting SSH2_MSG_NEWKEYS\ndebug1: SSH2_MSG_NEWKEYS received\ndebug1: rekey in after 134217728 blocks\ndebug1: pubkey_prepare: ssh_get_authentication_socket: No such file or directory\ndebug1: Will attempt key: C:\\\\Users\\\\LL L/.ssh/id_rsa RSA SHA256:SzTwSmfmiLOTlZGuTIhP2VctForj8wVH866bFSWWLH0\ndebug1: Will attempt key: C:\\\\Users\\\\LL L/.ssh/id_dsa\ndebug1: Will attempt key: C:\\\\Users\\\\LL L/.ssh/id_ecdsa\ndebug1: Will attempt key: C:\\\\Users\\\\LL L/.ssh/id_ed25519\ndebug1: Will attempt key: C:\\\\Users\\\\LL L/.ssh/id_xmss\ndebug1: SSH2_MSG_SERVICE_ACCEPT received\ndebug1: Authentications that can continue: publickey\ndebug1: Next authentication method: publickey\ndebug1: Offering public key: C:\\\\Users\\\\LL L/.ssh/id_rsa RSA SHA256:SzTwSmfmiLOTlZGuTIhP2VctForj8wVH866bFSWWLH0\ndebug1: Server accepts key: C:\\\\Users\\\\LL L/.ssh/id_rsa RSA SHA256:SzTwSmfmiLOTlZGuTIhP2VctForj8wVH866bFSWWLH0\ndebug1: Authentication succeeded (publickey).\nAuthenticated to e.coding.net ([81.69.155.167]:22).\ndebug1: channel 0: new [client-session]\ndebug1: Entering interactive session.\ndebug1: pledge: network\nCODING 提示: Hello eyl, You've connected to coding.net via SSH. This is a Personal Key.\neyl，你好，你已经通过 SSH 协议认证 coding.net 服务，这是一个个人公钥.\n公钥指纹：e9:6c:54:c8:72:42:36:ac:b2:29:7e:ad:b1:a5:09:42\ndebug1: client_input_channel_req: channel 0 rtype exit-status reply 0\ndebug1: channel 0: free: client-session, nchannels 1\nTransferred: sent 2624, received 1924 bytes, in 1.5 seconds\nBytes per second: sent 1791.8, received 1313.8\ndebug1: Exit status 0\n\nPlease review the rest of the bug report below.\nYou can delete any lines you don't wish to share.\n\n\n[System Info]\ngit version:\ngit version 2.33.1.windows.1\ncpu: x86_64\nbuilt from commit: 05d80adb775077d673fab685009ede4a1003ed92\nsizeof-long: 4\nsizeof-size_t: 8\nshell-path: /bin/sh\nfeature: fsmonitor--daemon\nuname: Windows 10.0 19044 \ncompiler info: gnuc: 10.3\nlibc info: no libc information available\n$SHELL (typically, interactive shell): \n\n\n[Enabled Hooks]\n\n\n\n"},{"id":"439013","messageId":"CAGyf7-GV62dHzsiV7KD2h8Rgg2HBWn1TgimodzcPUWravowUGQ@mail.gmail.com","threadId":"56736","inReplyTo":"001401d7c490$e7d57620$b7806260$@xeltek-cn.com","subject":"Re: Git failed to pull after upgrading to 2.33.1, using choco","fromName":"Bryan Turner","fromEmail":"bturner@atlassian.com","sentAt":"2021-10-19T02:48:59Z","receivedAt":"2021-10-19T02:49:14Z","isPatch":false,"sender":{"key":"bturner@atlassian.com","avatar":"https://gravatar.com/avatar/16bcf3167981c1ef7c804e502642366d888a35b0d0b0a4ca01fdc442aa1acb1e?d=mp&s=160"},"body":"On Mon, Oct 18, 2021 at 7:34 PM LL L wrote:\n>\n> Thank you for filling out a Git bug report!\n> Please answer the following questions to help us understand your issue.\n>\n> What did you do before the bug happened? (Steps to reproduce your issue)\n>\n> 1. uninstall git for windows 2.32.2\n> 2. install git again with： choco install -y git\n> 3. git pull emit error:\n>\n> git@e.coding.net: Permission denied (publickey).\n> fatal: Could not read from remote repository.\n>\n> Please make sure you have the correct access rights\n> and the repository exists.\n>\n> 4. I am sure it is caused by the upgrading, I observed same issue on my other windows 10 machine..\n>\n> What did you expect to happen? (Expected behavior)\n>\n> pull from origin;\n>\n> What happened instead? (Actual behavior)\n>\n> git@e.coding.net: Permission denied (publickey).\n> fatal: Could not read from remote repository.\n>\n> Please make sure you have the correct access rights\n> and the repository exists.\n\nMost likely you're running afoul of an OpenSSH 8.8p1 upgrade in Git\nfor Windows 2.33. OpenSSH 8.8 disables ssh-rsa key exchanges by\ndefault[1], which results in this sort of error. Git for Windows\n2.32.2 was using OpenSSH 8.7 (or perhaps OpenSSH 8.5).\n\n[1] https://www.openssh.com/txt/release-8.8; see the\n\"Potentially-incompatible changes\" section.\n\n>\n> What's different between what you expected and what actually happened?\n>\n> It doesn't work.\n>\n> Anything else you want to add:\n>\n> coding:/mytex on  trunk [?]\n> ❯ git pull\n> git@e.coding.net: Permission denied (publickey).\n> fatal: Could not read from remote repository.\n>\n> Please make sure you have the correct access rights\n> and the repository exists.\n>\n> coding:/mytex on  trunk [?] took 13s\n> ❯ ssh -Tv git@e.coding.net\n> OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2\n\nThese details end up being for the OpenSSH Windows package, which is\n_not_ the SSH being used by your Git for Windows install--it's almost\ncertainly using the bundled OpenSSH 8.8p1. You should double check by\nexplicitly running the ssh.exe that's in your Git for Windows install\ninstead.\n\n> debug1: Reading configuration data C:\\\\Users\\\\LL L/.ssh/config\n> debug1: Connecting to e.coding.net [81.69.155.167] port 22.\n> debug1: Connection established.\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_rsa type 0\n\nSo you're using an RSA key. This may be a problem.\n\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_rsa-cert type -1\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_dsa type -1\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_dsa-cert type -1\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_ecdsa type -1\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_ecdsa-cert type -1\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_ed25519 type -1\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_ed25519-cert type -1\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_xmss type -1\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_xmss-cert type -1\n> debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.1\n> debug1: Remote protocol version 2.0, remote software version Go-CodingGit\n> debug1: no match: Go-CodingGit\n> debug1: Authenticating to e.coding.net:22 as 'git'\n> debug1: SSH2_MSG_KEXINIT sent\n> debug1: SSH2_MSG_KEXINIT received\n> debug1: kex: algorithm: curve25519-sha256@libssh.org\n> debug1: kex: host key algorithm: rsa-sha2-512\n\nLooks like the server supports more secure RSA key exchanges, which is good.\n\n> debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: compression: none\n> debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: compression: none\n> debug1: expecting SSH2_MSG_KEX_ECDH_REPLY\n> debug1: Server host key: ssh-rsa SHA256:jok3FH7q5LJ6qvE7iPNehBgXRw51ErE77S0Dn+Vg/Ik\n> debug1: Host 'e.coding.net' is known and matches the RSA host key.\n> debug1: Found key in C:\\\\Users\\\\LL L/.ssh/known_hosts:28\n> debug1: rekey out after 134217728 blocks\n> debug1: SSH2_MSG_NEWKEYS sent\n> debug1: expecting SSH2_MSG_NEWKEYS\n> debug1: SSH2_MSG_NEWKEYS received\n> debug1: rekey in after 134217728 blocks\n> debug1: pubkey_prepare: ssh_get_authentication_socket: No such file or directory\n> debug1: Will attempt key: C:\\\\Users\\\\LL L/.ssh/id_rsa RSA SHA256:SzTwSmfmiLOTlZGuTIhP2VctForj8wVH866bFSWWLH0\n> debug1: Will attempt key: C:\\\\Users\\\\LL L/.ssh/id_dsa\n> debug1: Will attempt key: C:\\\\Users\\\\LL L/.ssh/id_ecdsa\n> debug1: Will attempt key: C:\\\\Users\\\\LL L/.ssh/id_ed25519\n> debug1: Will attempt key: C:\\\\Users\\\\LL L/.ssh/id_xmss\n> debug1: SSH2_MSG_SERVICE_ACCEPT received\n> debug1: Authentications that can continue: publickey\n> debug1: Next authentication method: publickey\n> debug1: Offering public key: C:\\\\Users\\\\LL L/.ssh/id_rsa RSA SHA256:SzTwSmfmiLOTlZGuTIhP2VctForj8wVH866bFSWWLH0\n> debug1: Server accepts key: C:\\\\Users\\\\LL L/.ssh/id_rsa RSA SHA256:SzTwSmfmiLOTlZGuTIhP2VctForj8wVH866bFSWWLH0\n> debug1: Authentication succeeded (publickey).\n> Authenticated to e.coding.net ([81.69.155.167]:22).\n> debug1: channel 0: new [client-session]\n> debug1: Entering interactive session.\n> debug1: pledge: network\n> CODING 提示: Hello eyl, You've connected to coding.net via SSH. This is a Personal Key.\n> eyl，你好，你已经通过 SSH 协议认证 coding.net 服务，这是一个个人公钥.\n> 公钥指纹：e9:6c:54:c8:72:42:36:ac:b2:29:7e:ad:b1:a5:09:42\n> debug1: client_input_channel_req: channel 0 rtype exit-status reply 0\n> debug1: channel 0: free: client-session, nchannels 1\n> Transferred: sent 2624, received 1924 bytes, in 1.5 seconds\n> Bytes per second: sent 1791.8, received 1313.8\n> debug1: Exit status 0\n>\n> Please review the rest of the bug report below.\n> You can delete any lines you don't wish to share.\n>\n>\n> [System Info]\n> git version:\n> git version 2.33.1.windows.1\n> cpu: x86_64\n> built from commit: 05d80adb775077d673fab685009ede4a1003ed92\n> sizeof-long: 4\n> sizeof-size_t: 8\n> shell-path: /bin/sh\n> feature: fsmonitor--daemon\n> uname: Windows 10.0 19044\n> compiler info: gnuc: 10.3\n> libc info: no libc information available\n> $SHELL (typically, interactive shell): \n>\n>\n> [Enabled Hooks]\n>\n>\n>\n"},{"id":"439014","messageId":"01c301d7c494$fdf33f60$f9d9be20$@xeltek-cn.com","threadId":"56736","inReplyTo":"CAGyf7-GV62dHzsiV7KD2h8Rgg2HBWn1TgimodzcPUWravowUGQ@mail.gmail.com","subject":"答复: Git failed to pull after upgrading to 2.33.1, using choco","fromName":"LL L","fromEmail":"lll@xeltek-cn.com","sentAt":"2021-10-19T02:57:01Z","receivedAt":"2021-10-19T02:57:10Z","isPatch":false,"sender":{"key":"lll@xeltek-cn.com","avatar":null},"body":"-----邮件原件-----\n发件人: Bryan Turner [mailto:bturner@atlassian.com] \n发送时间: Tuesday, October 19, 2021 10:49 AM\n收件人: LL L \n抄送: Git Users \n主题: Re: Git failed to pull after upgrading to 2.33.1, using choco\n\nOn Mon, Oct 18, 2021 at 7:34 PM LL L wrote:\n>\n> Thank you for filling out a Git bug report!\n> Please answer the following questions to help us understand your issue.\n>\n> What did you do before the bug happened? (Steps to reproduce your \n> issue)\n>\n> 1. uninstall git for windows 2.32.2\n> 2. install git again with： choco install -y git 3. git pull emit \n> error:\n>\n> git@e.coding.net: Permission denied (publickey).\n> fatal: Could not read from remote repository.\n>\n> Please make sure you have the correct access rights and the repository \n> exists.\n>\n> 4. I am sure it is caused by the upgrading, I observed same issue on my other windows 10 machine..\n>\n> What did you expect to happen? (Expected behavior)\n>\n> pull from origin;\n>\n> What happened instead? (Actual behavior)\n>\n> git@e.coding.net: Permission denied (publickey).\n> fatal: Could not read from remote repository.\n>\n> Please make sure you have the correct access rights and the repository \n> exists.\n\nMost likely you're running afoul of an OpenSSH 8.8p1 upgrade in Git for Windows 2.33. OpenSSH 8.8 disables ssh-rsa key exchanges by default[1], which results in this sort of error. Git for Windows\n2.32.2 was using OpenSSH 8.7 (or perhaps OpenSSH 8.5).\n\n[1] https://www.openssh.com/txt/release-8.8; see the \"Potentially-incompatible changes\" section.\n\n>\n> What's different between what you expected and what actually happened?\n>\n> It doesn't work.\n>\n> Anything else you want to add:\n>\n> coding:/mytex on  trunk [?]\n> ❯ git pull\n> git@e.coding.net: Permission denied (publickey).\n> fatal: Could not read from remote repository.\n>\n> Please make sure you have the correct access rights and the repository \n> exists.\n>\n> coding:/mytex on  trunk [?] took 13s\n> ❯ ssh -Tv git@e.coding.net\n> OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2\n\nThese details end up being for the OpenSSH Windows package, which is _not_ the SSH being used by your Git for Windows install--it's almost certainly using the bundled OpenSSH 8.8p1. You should double check by explicitly running the ssh.exe that's in your Git for Windows install instead.\n\n> debug1: Reading configuration data C:\\\\Users\\\\LL L/.ssh/config\n> debug1: Connecting to e.coding.net [81.69.155.167] port 22.\n> debug1: Connection established.\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_rsa type 0\n\nSo you're using an RSA key. This may be a problem.\n\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_rsa-cert type -1\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_dsa type -1\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_dsa-cert type -1\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_ecdsa type -1\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_ecdsa-cert type -1\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_ed25519 type -1\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_ed25519-cert type -1\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_xmss type -1\n> debug1: identity file C:\\\\Users\\\\LL L/.ssh/id_xmss-cert type -1\n> debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.1\n> debug1: Remote protocol version 2.0, remote software version \n> Go-CodingGit\n> debug1: no match: Go-CodingGit\n> debug1: Authenticating to e.coding.net:22 as 'git'\n> debug1: SSH2_MSG_KEXINIT sent\n> debug1: SSH2_MSG_KEXINIT received\n> debug1: kex: algorithm: curve25519-sha256@libssh.org\n> debug1: kex: host key algorithm: rsa-sha2-512\n\nLooks like the server supports more secure RSA key exchanges, which is good.\n\n> debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: \n> compression: none\n> debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: \n> compression: none\n> debug1: expecting SSH2_MSG_KEX_ECDH_REPLY\n> debug1: Server host key: ssh-rsa \n> SHA256:jok3FH7q5LJ6qvE7iPNehBgXRw51ErE77S0Dn+Vg/Ik\n> debug1: Host 'e.coding.net' is known and matches the RSA host key.\n> debug1: Found key in C:\\\\Users\\\\LL L/.ssh/known_hosts:28\n> debug1: rekey out after 134217728 blocks\n> debug1: SSH2_MSG_NEWKEYS sent\n> debug1: expecting SSH2_MSG_NEWKEYS\n> debug1: SSH2_MSG_NEWKEYS received\n> debug1: rekey in after 134217728 blocks\n> debug1: pubkey_prepare: ssh_get_authentication_socket: No such file or \n> directory\n> debug1: Will attempt key: C:\\\\Users\\\\LL L/.ssh/id_rsa RSA \n> SHA256:SzTwSmfmiLOTlZGuTIhP2VctForj8wVH866bFSWWLH0\n> debug1: Will attempt key: C:\\\\Users\\\\LL L/.ssh/id_dsa\n> debug1: Will attempt key: C:\\\\Users\\\\LL L/.ssh/id_ecdsa\n> debug1: Will attempt key: C:\\\\Users\\\\LL L/.ssh/id_ed25519\n> debug1: Will attempt key: C:\\\\Users\\\\LL L/.ssh/id_xmss\n> debug1: SSH2_MSG_SERVICE_ACCEPT received\n> debug1: Authentications that can continue: publickey\n> debug1: Next authentication method: publickey\n> debug1: Offering public key: C:\\\\Users\\\\LL L/.ssh/id_rsa RSA \n> SHA256:SzTwSmfmiLOTlZGuTIhP2VctForj8wVH866bFSWWLH0\n> debug1: Server accepts key: C:\\\\Users\\\\LL L/.ssh/id_rsa RSA \n> SHA256:SzTwSmfmiLOTlZGuTIhP2VctForj8wVH866bFSWWLH0\n> debug1: Authentication succeeded (publickey).\n> Authenticated to e.coding.net ([81.69.155.167]:22).\n> debug1: channel 0: new [client-session]\n> debug1: Entering interactive session.\n> debug1: pledge: network\n> CODING 提示: Hello eyl, You've connected to coding.net via SSH. This is a Personal Key.\n> eyl，你好，你已经通过 SSH 协议认证 coding.net 服务，这是一个个人公钥.\n> 公钥指纹：e9:6c:54:c8:72:42:36:ac:b2:29:7e:ad:b1:a5:09:42\n> debug1: client_input_channel_req: channel 0 rtype exit-status reply 0\n> debug1: channel 0: free: client-session, nchannels 1\n> Transferred: sent 2624, received 1924 bytes, in 1.5 seconds Bytes per \n> second: sent 1791.8, received 1313.8\n> debug1: Exit status 0\n>\n> Please review the rest of the bug report below.\n> You can delete any lines you don't wish to share.\n>\n>\n> [System Info]\n> git version:\n> git version 2.33.1.windows.1\n> cpu: x86_64\n> built from commit: 05d80adb775077d673fab685009ede4a1003ed92\n> sizeof-long: 4\n> sizeof-size_t: 8\n> shell-path: /bin/sh\n> feature: fsmonitor--daemon\n> uname: Windows 10.0 19044\n> compiler info: gnuc: 10.3\n> libc info: no libc information available $SHELL (typically, \n> interactive shell): \n>\n>\n> [Enabled Hooks]\n>\n>\n>\n\nThanks. Really appreciated. I will check it out.\n\n\n\n"},{"id":"439057","messageId":"YW9SmwZOp+HYHScP@camp.crustytoothpaste.net","threadId":"56736","inReplyTo":"CAGyf7-GV62dHzsiV7KD2h8Rgg2HBWn1TgimodzcPUWravowUGQ@mail.gmail.com","subject":"Re: Git failed to pull after upgrading to 2.33.1, using choco","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2021-10-19T23:19:55Z","receivedAt":"2021-10-19T23:20:34Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2021-10-19 at 02:48:59, Bryan Turner wrote:\n> On Mon, Oct 18, 2021 at 7:34 PM LL L wrote:\n> >\n> > What happened instead? (Actual behavior)\n> >\n> > git@e.coding.net: Permission denied (publickey).\n> > fatal: Could not read from remote repository.\n> >\n> > Please make sure you have the correct access rights\n> > and the repository exists.\n> \n> Most likely you're running afoul of an OpenSSH 8.8p1 upgrade in Git\n> for Windows 2.33. OpenSSH 8.8 disables ssh-rsa key exchanges by\n> default[1], which results in this sort of error. Git for Windows\n> 2.32.2 was using OpenSSH 8.7 (or perhaps OpenSSH 8.5).\n> \n> [1] https://www.openssh.com/txt/release-8.8; see the\n> \"Potentially-incompatible changes\" section.\n\nYes, this is almost certainly the problem. Note that this change was\nmade because while RSA _keys_ are still secure, the SHA-1 signatures\nbeing used are not, and so folks need to either use those RSA keys with\nSHA-2 or switch keys.\n\n> > debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.1\n> > debug1: Remote protocol version 2.0, remote software version Go-CodingGit\n> > debug1: no match: Go-CodingGit\n\nGo's SSH library is known to have various problems with RSA keys and\nSHA-2, so if this site is using that library, then it may be the cause\nof your problems. I know they're aware of this problem, so hopefully\nthey'll be able to work on it soon.\n\n> > debug1: Authenticating to e.coding.net:22 as 'git'\n> > debug1: SSH2_MSG_KEXINIT sent\n> > debug1: SSH2_MSG_KEXINIT received\n> > debug1: kex: algorithm: curve25519-sha256@libssh.org\n> > debug1: kex: host key algorithm: rsa-sha2-512\n> \n> Looks like the server supports more secure RSA key exchanges, which is good.\n\nThis is encouraging, but I don't think it's sufficient in this case.\n\nYou may want to generate a new Ed25519 SSH key with \"ssh-keygen -t\ned25519\" and use that instead, provided the site supports that. Many\nsites do, and those keys aren't subject to any of the problems you've\nseen here.\n-- \nbrian m. carlson (he/him or they/them)\nToronto, Ontario, CA\n"}]}