-
Notifications
You must be signed in to change notification settings - Fork 846
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
unable to git clone via ssh using core.sshcommand=ssh.exe #12145
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
The script will output the path of the log file once done. If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here Once completed please upload the output files to this Github issue. Click here for more info on logging View similar issuesPlease view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it! Open similar issues:
Closed similar issues:
|
incase anyone finds this later the solution/workaround i used was setting up an alias on wsl to use git.exe instead of git. also had to run the below commands from windows. git config --global credential.provider generic |
Windows Version
Microsoft Windows [Version 10.0.22631.4249]
WSL Version
2.3.24.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1
Distro Version
Ubuntu 22.04
Other Software
Windows OpenSSH (ssh.exe)
Repro Steps
Expected Behavior
It should show a prompt to accept or reject the unknown host key; and if you accept it, it should continue with the git clone.
Even after running
git config --global credential.helper "/mnt/c/Program\ Files/Git/mingw64/bin/git-credential-manager.exe"
it still hangsActual Behavior
It hangs forever, and there is no output.
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: