Changes between Initial Version and Version 1 of Ticket #2016
- Timestamp:
- 10/29/18 06:55:49 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2016
-
Property
Status
changed from
new
toclosed
-
Property
Resolution
changed from
to
fixed
-
Property
Status
changed from
-
Ticket #2016 – Description
initial v1 10 10 this didn't work anymore in the 2.4 client. Easy work-around, use the FQDN instead. 11 11 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.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. 13 13 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.pubinstead. (Easy fix).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). 15 15 16 16 From 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?