#2567 closed enhancement (fixed)
make ssh connections via paramiko more configurable
Reported by: | Antoine Martin | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | major | Milestone: | 4.0 |
Component: | network | Version: | 3.0.x |
Keywords: | Cc: |
Description (last modified by )
OpenSSH supports configuration options, both in its config file and using the command line.
We should provide a similar way of setting options:
- reading the openssh
ssh_config
if present - handling options in URL strings
See also:
Change History (6)
comment:1 Changed 13 months ago by
Description: | modified (diff) |
---|---|
Status: | new → assigned |
comment:2 Changed 13 months ago by
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
comment:3 Changed 13 months ago by
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Let's also make it possible to specify the keyfile to use.
comment:4 Changed 13 months ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
As of r25180, we can also specify paramiko attributes on the URI, including the key:
XPRA_SSH_DEFAULT_KEYFILES="" xpra attach "ssh://localhost/?key=$HOME/.ssh/id_rsa&auth=key"
The same options can still be specified as a general paramiko attribute:
XPRA_SSH_DEFAULT_KEYFILES="" xpra attach "ssh://localhost/" --ssh="paramiko:key=/home/antoine/.ssh/id_rsa,auth=key"
The new XPRA_SSH_DEFAULT_KEYFILES
env var is used in these examples to disable the default ssh key locations.
Important: the old URI format ssh:host/DISPLAY
is no longer supported. Parsing such strings was becoming increasingly unwieldy.
See also #2582.
comment:5 Changed 13 months ago by
comment:6 Changed 5 weeks ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2567
Note: See
TracTickets for help on using
tickets.
Done in r25103.
Self-explanatory examples (add
--debug=ssh
for debugging):