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

#2016 closed defect (fixed)

ssh feature loss vs 2.2.4 client macos

Reported by: sto6 Owned by: Antoine Martin
Priority: minor Milestone: 2.5
Component: client Version: 2.4.x
Keywords: ssh macos Cc:

Description (last modified by Antoine Martin)

I had been using Xpra client 2.2.4 on macos 10.13.6
then upgraded (using the .pkg) to xpra v2.4-r20679.

  1. Previously my hostname was a short alias "joe", configured in the .ssh/config using a Host line like:
Host joe joe.example.com

this didn't work anymore in the 2.4 client. Easy work-around, use the FQDN instead.

  1. 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.

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).

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?

Change History (2)

comment:1 Changed 4 years ago by Antoine Martin

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

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".

comment:2 Changed 16 months ago by migration script

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

Note: See TracTickets for help on using tickets.