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
Partial hang fix from #520 breaks proxy sockets #774
Labels
Milestone
Comments
This was referenced Jul 20, 2016
Closed
Spliced gateway support into Fabric 2 & confirmed this myself under Python 3. Fix inbound. |
Hi, after installing 2.0.2, I'm still getting the same error when using ProxyCommand:
|
Well that'd be because |
dkhapun
pushed a commit
to cyberx-labs/paramiko
that referenced
this issue
Jun 7, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
An anonymous user noted via email that the partial fix committed earlier for #520 breaks on the "using a
Channel
as a proxy socket" use case (as seen eg via Fabric withenv.gateway
set - though I think this user was doing it independently of that).Specifically, the issue happens because socket objects (under Py3) exhibit
._closed
, butChannel
objects exhibit.closed
. Since the earlier fix branches into a test ofsock._closed
under Python 3, anAttributeError
is raised:As this user suggests, I think a simple
hasattr
test added to the mix ought to suffice; this would also help with situations wheresocket.closed
becomes a real API (ISTR confusion on this point during dev of the earlier fix anyways - but that was probably Python 2 vs 3.)The text was updated successfully, but these errors were encountered: