Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't clone GitHub repo with ssh on Windows #4875

Closed
St0wy opened this issue Nov 15, 2024 · 2 comments
Closed

Can't clone GitHub repo with ssh on Windows #4875

St0wy opened this issue Nov 15, 2024 · 2 comments

Comments

@St0wy
Copy link

St0wy commented Nov 15, 2024

Description

When cloning I get :

jj git clone [email protected]:St0wy/Learn-Direct3D-11.git
Fetching into new repo in "\\?\C:\dev\odin\Learn-Direct3D-11"
Error: failed to authenticate SSH session: ; class=Ssh (23)
Hint: Jujutsu uses libssh2, which doesn't respect ~/.ssh/config. Does `ssh -F /dev/null` to the host work?

I have an RSA key setup that works with git clone.

ssh -F /dev/null [email protected] also seems to work.

ssh -F /dev/null [email protected]
PTY allocation request failed on channel 0
Hi St0wy! You've successfully authenticated, but GitHub does not provide shell access.

Enabling debug output seems to show that it found the key, maybe it's the username part that is wrong ?

2024-11-15T20:27:47.544551Z  INFO run_command:fetch{remote_name="origin" branch_names=[Substring("")] git_settings=GitSettings { auto_local_bookmark: false, abandon_unreachable_commits: true } depth=None}: jj_lib::git: trying ssh_key username="git" path="C:\\Users\\stowy\\.ssh\\id_rsa"

Steps to Reproduce the Problem

  1. Clone a GitHub repo on Windows via ssh

Expected Behavior

Should clone the repo without error.

Actual Behavior

Can't clone the repo.

Specifications

  • Platform: Windows 11
  • Version: 0.23.0
@St0wy
Copy link
Author

St0wy commented Nov 15, 2024

Update, using this version fixes the issue : #3191

Should the issue be closed ?

@martinvonz
Copy link
Member

This sounds similar enough to #3322 that I think we can at least close it as a duplicate of that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants