git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "LL L" <lll@xeltek-cn.com>
To: <git@vger.kernel.org>
Subject: Git failed to pull after upgrading to 2.33.1, using choco
Date: Tue, 19 Oct 2021 10:27:43 +0800	[thread overview]
Message-ID: <001401d7c490$e7d57620$b7806260$@xeltek-cn.com> (raw)

Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)

1. uninstall git for windows 2.32.2
2. install git again with: choco install -y git
3. git pull emit error:

git@e.coding.net: Permission denied (publickey).
fatal: Could not read from remote repository.

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

4. I am sure it is caused by the upgrading, I observed same issue on my other windows 10 machine..

What did you expect to happen? (Expected behavior)

pull from origin;

What happened instead? (Actual behavior)

git@e.coding.net: Permission denied (publickey).
fatal: Could not read from remote repository.

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

What's different between what you expected and what actually happened?

It doesn't work.

Anything else you want to add:

coding:/mytex on  trunk [?]
❯ git pull
git@e.coding.net: Permission denied (publickey).
fatal: Could not read from remote repository.

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

coding:/mytex on  trunk [?] took 13s
❯ ssh -Tv git@e.coding.net
OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
debug1: Reading configuration data C:\\Users\\LL L/.ssh/config
debug1: Connecting to e.coding.net [81.69.155.167] port 22.
debug1: Connection established.
debug1: identity file C:\\Users\\LL L/.ssh/id_rsa type 0
debug1: identity file C:\\Users\\LL L/.ssh/id_rsa-cert type -1
debug1: identity file C:\\Users\\LL L/.ssh/id_dsa type -1
debug1: identity file C:\\Users\\LL L/.ssh/id_dsa-cert type -1
debug1: identity file C:\\Users\\LL L/.ssh/id_ecdsa type -1
debug1: identity file C:\\Users\\LL L/.ssh/id_ecdsa-cert type -1
debug1: identity file C:\\Users\\LL L/.ssh/id_ed25519 type -1
debug1: identity file C:\\Users\\LL L/.ssh/id_ed25519-cert type -1
debug1: identity file C:\\Users\\LL L/.ssh/id_xmss type -1
debug1: identity file C:\\Users\\LL L/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.1
debug1: Remote protocol version 2.0, remote software version Go-CodingGit
debug1: no match: Go-CodingGit
debug1: Authenticating to e.coding.net:22 as 'git'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256@libssh.org
debug1: kex: host key algorithm: rsa-sha2-512
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-rsa SHA256:jok3FH7q5LJ6qvE7iPNehBgXRw51ErE77S0Dn+Vg/Ik
debug1: Host 'e.coding.net' is known and matches the RSA host key.
debug1: Found key in C:\\Users\\LL L/.ssh/known_hosts:28
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: pubkey_prepare: ssh_get_authentication_socket: No such file or directory
debug1: Will attempt key: C:\\Users\\LL L/.ssh/id_rsa RSA SHA256:SzTwSmfmiLOTlZGuTIhP2VctForj8wVH866bFSWWLH0
debug1: Will attempt key: C:\\Users\\LL L/.ssh/id_dsa
debug1: Will attempt key: C:\\Users\\LL L/.ssh/id_ecdsa
debug1: Will attempt key: C:\\Users\\LL L/.ssh/id_ed25519
debug1: Will attempt key: C:\\Users\\LL L/.ssh/id_xmss
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: C:\\Users\\LL L/.ssh/id_rsa RSA SHA256:SzTwSmfmiLOTlZGuTIhP2VctForj8wVH866bFSWWLH0
debug1: Server accepts key: C:\\Users\\LL L/.ssh/id_rsa RSA SHA256:SzTwSmfmiLOTlZGuTIhP2VctForj8wVH866bFSWWLH0
debug1: Authentication succeeded (publickey).
Authenticated to e.coding.net ([81.69.155.167]:22).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: pledge: network
CODING 提示: Hello eyl, You've connected to coding.net via SSH. This is a Personal Key.
eyl,你好,你已经通过 SSH 协议认证 coding.net 服务,这是一个个人公钥.
公钥指纹:e9:6c:54:c8:72:42:36:ac:b2:29:7e:ad:b1:a5:09:42
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: client-session, nchannels 1
Transferred: sent 2624, received 1924 bytes, in 1.5 seconds
Bytes per second: sent 1791.8, received 1313.8
debug1: Exit status 0

Please review the rest of the bug report below.
You can delete any lines you don't wish to share.


[System Info]
git version:
git version 2.33.1.windows.1
cpu: x86_64
built from commit: 05d80adb775077d673fab685009ede4a1003ed92
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Windows 10.0 19044 
compiler info: gnuc: 10.3
libc info: no libc information available
$SHELL (typically, interactive shell): <unset>


[Enabled Hooks]




             reply	other threads:[~2021-10-19  2:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19  2:27 LL L [this message]
2021-10-19  2:48 ` Git failed to pull after upgrading to 2.33.1, using choco Bryan Turner
2021-10-19  2:57   ` 答复: " LL L
2021-10-19 23:19   ` brian m. carlson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001401d7c490$e7d57620$b7806260$@xeltek-cn.com' \
    --to=lll@xeltek-cn.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).