8000 ssh-agent on windows: failed connecting agent · Issue #4958 · libgit2/libgit2 · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

ssh-agent on windows: failed connecting agent #4958

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.

Sign up for GitHub

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

Jump to bottom
Open
jeroen opened this issue Jan 24, 2019 · 1 comment
Open

ssh-agent on windows: failed connecting agent #4958

jeroen opened this issue Jan 24, 2019 · 1 comment

Comments

@jeroen
Copy link
Contributor
jeroen commented Jan 24, 2019

Summary

The official git for windows contains a great ssh-agent, but git_cred_ssh_key_from_agent() does not seem to be able to use it. It is unclear why.

Reproduce

Once installed, git for Windows puts a special script start-ssh-agent on the PATH which will start the agent (if needed) from a windows shell and set the SSH_AUTH_SOCK and SSH_AGENT_PID variables.

screen shot 2019-01-24 at 2 55 50 pm

Now the shell variables are set to e.g below and the git command line will use the agent.

SSH_AGENT_PID=3584
SSH_AUTH_SOCK=/tmp/ssh-lxTliF4IDExJ/agent.3520

However git_cred_ssh_key_from_agent() seems unable to connect to this. It will always errors with error authenticating: failed connecting agent.

Question

Is this expected to work at all? My libgit2 is built with the latest libssh2 using the standard gcc mingw-w64 toolchain. How can I further debug this?
jeroen added a commit to r-lib/credentials that referenced this issue Jan 24, 2019
@jeroen
Disable agent on Windows because it does not work right now, see libg…
30152e4 
…it2/libgit2#4958
@jeroen
Copy link
Contributor Author
jeroen commented Jan 25, 2019 •
edited
Loading

Update This error message comes form libssh2 putty agent client. It seems like libssh2 is hardcoded to use putty agent on windows, due to the lack of availability of unix sockets.

I don't understand how git 4 windows does this though.

@notheotherben notheotherben mentioned this issue Aug 7, 2019
Closed
@zachshattuck zachshattuck mentioned this issue Oct 28, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jeroen
0