-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
paramiko client on windows cannot connect to ssh-agent, agent requests hang #4353
Comments
This doesn't look like the python that we ship. Looking at the paramiko source, this is the context:
I'm not sure if having an |
No. Unfortunately |
It looks like it simply isn't implemented on windows: Could you maybe disable agent forwarding on windows to avoid hangs when the agent is accessed on the remote system? |
I believe the other agents do work - so the solution might be to block the import of |
Please try the 6.2-r36663 or later beta builds which include 9e98dbd - does that work for you? Ideally paramiko would fix this bug - but seeing that even trivial fixes with unit tests aren't being merged, I seriously doubt it. |
Prevention of the module import of
But the forwarding channel is still activated and using the agent on the remote side still blocks and causes the same exception on the client:
|
It turns out that paramiko already does its own checks before loading the agent: So I think I will revert my blocking change. The openssh agent should work if the pipe is found. What we may need to do instead is to check if a local agent is actually available before enabling agent forwarding on the server side. xpra_cmd.exe --env=XPRA_SSH_AGENT_DISPATCH=0 ... This should be forwarded to the remote start command and will disable agent forwarding for the server session. |
Makes sense.
Unfortunately that is still not true on my system even though the openssh agent is running and working:
Accessing the agent on the remote host still blocks with the above Does openssh agent forwarding acually work in your windows test environment? I'd be suprised because I don't think that this will work on Windows:
This doesn't work for me. It still enables a forwarding channel and connects the remote agent to it:
On the remote side:
|
Btw (unrelated): The windows test build outputs this exception on every window draw: (those messages appear really often!)
|
Fixed in 4ead552
Actually, this is wrong: we can just always enable agent forwarding, but the server should make this point to the default socket path when the client doesn't support agent forwarding.
Ouch.
I don't use it myself, but I'm pretty sure that I had tested with pageant when the ssh agent feature was released (#2303) |
On my windows 10 client, the builtin paramiko ssh client enables ssh agent forwarding but cannot connect to the running ssh agent.
Trying to use agent forwarding blocks because paramiko cannot contact the agent:
Remote system (linux):
At the same time his request raises the following exception at the local windows client:
However the agent is running: (tested in the same cmd window)
Using
--ssh="plink -A"
works but putty uses pageant and I'd prefer the openssh agent.The text was updated successfully, but these errors were encountered: