xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.

Opened 4 years ago

Closed 4 years ago

Last modified 16 months ago

#2020 closed defect (duplicate)

"paramiko" support silently ignores ssh config

Reported by: reimar Owned by: Antoine Martin
Priority: major Milestone: 2.5
Component: client Version: 2.4.x
Keywords: Cc:

Description (last modified by Antoine Martin)

xpra started failing for me with this error:

xpra initialization error:
 cannot get IPv4 address of ('wpc', 22): [Errno -2] Name or service not known

This seems due to using "paramiko" instead of actual ssh, which means any ssh configuration is suddenly silently ignored (in this case, a host alias to go via a proxy).
There should at least be a warning that ssh is not used and thus any settings in .ssh/config are ignored, and also a hint on how to get the old behaviour back.
Even better would be some kind of automatic fallback on connection issues.

As there might also be more subtle failures (like suddenly not using a privacy-protecting VPN) I would however suggest to reconsider the change in default ssh client in general, until either paramiko can parse .ssh/config or at least there are some basic checks on .ssh/config not containing anything critical. Or until a major version bump...

Change History (2)

comment:1 Changed 4 years ago by Antoine Martin

Description: modified (diff)
Resolution: duplicate
Status: newclosed

comment:2 Changed 16 months ago by migration script

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2020

Note: See TracTickets for help on using tickets.