SSH

[xxxxxyang]

Select Topic Area

Question

Body

I have added the correct ssh_id_rsa_pub to my github account. However when I try to use it to connect my remote repositories, it doesn't work. This is the concrete information:


Looking forward to your answer, thank you!

[jdevfullstack]

can you paste that as text ? it's unreadable as image,

[xxxxxyang]

OpenSSH_for_Windows_8.1p1, LibreSSL 3.0.2
debug1: Reading configuration data C:\\Users\\x'yang/.ssh/config
debug1: Connecting to github.com [127.0.0.1] port 22.
debug1: Connection established.
debug1: identity file C:\\Users\\x'yang/.ssh/id_rsa type 0
debug1: identity file C:\\Users\\x'yang/.ssh/id_rsa-cert type -1
debug1: identity file C:\\Users\\x'yang/.ssh/id_dsa type -1
debug1: identity file C:\\Users\\x'yang/.ssh/id_dsa-cert type -1
debug1: identity file C:\\Users\\x'yang/.ssh/id_ecdsa type -1
debug1: identity file C:\\Users\\x'yang/.ssh/id_ecdsa-cert type -1
debug1: identity file C:\\Users\\x'yang/.ssh/id_ed25519 type -1
debug1: identity file C:\\Users\\x'yang/.ssh/id_ed25519-cert type -1
debug1: identity file C:\\Users\\x'yang/.ssh/id_xmss type -1
debug1: identity file C:\\Users\\x'yang/.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 OpenSSH_for_Windows_8.1
debug1: match: OpenSSH_for_Windows_8.1 pat OpenSSH* compat 0x04000000
debug1: Authenticating to github.com:22 as 'git'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
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: ecdsa-sha2-nistp256 SHA256:HFRtz6JjETicSyNZMTx+hW2BFvAieRBvU4QzMG5lC78
debug1: Host 'github.com' is known and matches the ECDSA host key.
debug1: Found key in C:\\Users\\x'yang/.ssh/known_hosts:9
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: Will attempt key: C:\\Users\\x'yang/.ssh/id_rsa RSA SHA256:79uzZOk7Wi5fFIe3YPqovldtJAweCkkdggNcAyBbIZg agent
debug1: Will attempt key: 3042308732@qq.com RSA SHA256:/fVmOE+YdbqxqZjy4yxbdtVZY1qpkzL+Ay16UYy27uU agent
debug1: Will attempt key: C:\\Users\\x'yang/.ssh/id_dsa
debug1: Will attempt key: C:\\Users\\x'yang/.ssh/id_ecdsa
debug1: Will attempt key: C:\\Users\\x'yang/.ssh/id_ed25519
debug1: Will attempt key: C:\\Users\\x'yang/.ssh/id_xmss
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering public key: C:\\Users\\x'yang/.ssh/id_rsa RSA SHA256:79uzZOk7Wi5fFIe3YPqovldtJAweCkkdggNcAyBbIZg agent
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Offering public key: 3042308732@qq.com RSA SHA256:/fVmOE+YdbqxqZjy4yxbdtVZY1qpkzL+Ay16UYy27uU agent
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Trying private key: C:\\Users\\x'yang/.ssh/id_dsa
debug1: Trying private key: C:\\Users\\x'yang/.ssh/id_ecdsa
debug1: Trying private key: C:\\Users\\x'yang/.ssh/id_ed25519
debug1: Trying private key: C:\\Users\\x'yang/.ssh/id_xmss
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: password
debug1: read_passphrase: can't open /dev/tty: No such file or directory
git@github.com's password:

sorry, this is debug text

[jdevfullstack]

Copilot might be of help,

---

The output you're seeing is from an attempt to connect to GitHub via SSH. It seems like the SSH client is not able to authenticate with the server. Here are a few things you could check:

1. SSH Key: Make sure you have a valid SSH key added to your GitHub account. You can check this by going to GitHub > Settings > SSH and GPG keys. If you don't have a key, you'll need to generate one and add it to your account.

2. SSH Agent: Ensure that your SSH agent is running and has your key added. You can check this by running ssh-add -l in your terminal. If your key is not listed, you can add it with ssh-add /path/to/your/key.

3. Correct Host: The log shows that you're trying to connect to github.com at IP address 127.0.0.1, which is the loopback address for your local machine. This is likely incorrect. Make sure your ~/.ssh/config file (or C:\\Users\\x'yang/.ssh/config on Windows) has the correct host configuration for GitHub.

4. Permissions: Ensure that your SSH key files have the correct permissions. On Unix systems, the private key file should be readable and writable only by the user, and not accessible by others (chmod 600 ~/.ssh/id_rsa).

5. Password Authentication: It seems like after failing to authenticate with public key, it's falling back to password authentication, which GitHub does not support for Git operations. You should only use SSH keys for authentication.

If you're still having trouble, you might want to consider using HTTPS instead of SSH for your GitHub connections. You can switch the remote URL of your repository from SSH to HTTPS with the following command:

git remote set-url origin https://github.com/username/repo.git

Replace username and repo with your GitHub username and the name of your repository.

[eymeen]

stop answering useless answers, anybody could get a better one from gpt

[jdevfullstack]

look all of those I helped, seems to me the one that can't help should shut up

and by the way, ChatGPT is not very particular with coding as it is trained on larger datasets and Copilot is more focused on coding, that's why other AIs are emerging too, you are too outdated by now

https://github.com/orgs/community/discussions?discussions_q=commenter%3Ajdevstatic+

[eymeen]

ok keep going then

[xxxxxyang]

Thanks for all your comments!
Seems that is ssh-agent problems

[LiteBrite82]

Hi @xxxxxyang

The GitHub documentation for SSH is pretty thorough as well.

As a side note, I would definitely delete any of the keys you have posted screenshots of.

P.S. I'm gonna move this question over to "Code Security" for maximum visibility. It could go to "Repositories" as well, but I think the "Code Security" community could have some extra insight.

Thanks for participating @jdevstatic @eymeen !

[eymeen]

Sorry for off-topic comment, can you check my question? #118693

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬