xpra icon
Bug tracker and wiki

Changes between Initial Version and Version 1 of Ticket #2016


Ignore:
Timestamp:
10/29/18 06:55:49 (10 months ago)
Author:
Antoine Martin
Comment:

2.4 with the new paramiko backend does not load config from .ssh, but 2.5 will: #1937

r20866 fixes the issue where it would only try the first key it finds, this will be included in 2.4.1 - thanks for reporting that

In the meantime, you can also switch back to the old openssh backend with --ssh="ssh -x".

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2016

    • Property Status changed from new to closed
    • Property Resolution changed from to fixed
  • Ticket #2016 – Description

    initial v1  
    1010this didn't work anymore in the 2.4 client. Easy work-around, use the FQDN instead.
    1111
    12 2. My ~/.ssh/ dir had and has both an id_rsa and id_dsa. A plain shell "ssh joe" did and does work to auto use id_dsa (no IdentityFile configured in .ssh/config). Using 2.2.4 client, it also auto used id_dsa.
     122. My ~/.ssh/ dir had and has both an id_rsa and id_dsa. A plain shell "ssh joe" did and does work to auto use id_dsa (no !IdentityFile configured in .ssh/config). Using 2.2.4 client, it also auto used id_dsa.
    1313
    14 In 2.4, the id_dsa did not work. And explicitly specifying it via IdentityFile in .ssh/config still failed to make it use it. I had to reconfigure remote account to use my id_rsa.pub instead. (Easy fix).
     14In 2.4, the id_dsa did not work. And explicitly specifying it via !IdentityFile in {{{.ssh/config}}} still failed to make it use it. I had to reconfigure remote account to use my {{{id_rsa.pub}}} instead. (Easy fix).
    1515
    1616From an earlier ticket 9 months ago, I recall statements like "blah not implemented or working yet in  python3/gtk3 client". Are these more like that?