#1924 closed defect (invalid)
version 2.4-20180721r19945M-1 no longer uses .ssh/config on Ubuntu Linux 17.10
Reported by: | Piskvor | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | major | Milestone: | 2.4 |
Component: | network | Version: | 2.3.x |
Keywords: | ssh | Cc: |
Description (last modified by )
I have a SSH alias "foo" in .ssh/config, which is actually bar.example.com. this works in anything that uses ssh and also used to work in xpra, up to and including previous version (r19937); now it doesn't work in current xpra version (r19945).
What I did:
xpra attach ssh:foo
What I expected to happen (as seen in previous versions since forever):
Xpra gtk2 client version 2.4-r19937 64-bit running on Linux Ubuntu 17.10 artful (...) Host key fingerprint is SHA256:0deadbeef0 Xpra X11 server version 1.0.1
What happened instead:
Xpra gtk2 client version 2.4-r19945 64-bit running on Linux Ubuntu 17.10 artful ssh: Could not resolve hostname foo: Name or service not known Error: failed to receive anything, not an xpra server?
Relevant ~/.ssh/config
section:
Host foo HostName bar.example.com Port 12345 User baz
Other tools using ssh are working correctly, previous version works. New version fails to use the SSH config, tries to resolve "foo" as a DNS name (which doesn't work, as the host is not reachable under that name from anywhere).
Change History (4)
comment:1 Changed 4 years ago by
Description: | modified (diff) |
---|---|
Milestone: | → 2.4 |
Resolution: | → invalid |
Status: | new → closed |
comment:2 Changed 4 years ago by
Excellent, thank you for the explanation and workaround.
(Yeah, one works with the servers one has, rather than the ones one would like to have)
comment:4 Changed 16 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1924
This is working as expected, the new native ssh implementation (#1646) knows nothing about openssh's configuration files.
If you want to revert to executing openssh as transport, use:
Yikes! 1.0.1!