xpra icon
Bug tracker and wiki

Changes between Initial Version and Version 2 of Ticket #2577


Ignore:
Timestamp:
02/05/20 17:39:32 (6 months ago)
Author:
Antoine Martin
Comment:

The connection works if I leave out --ssh="ssh -p 5222" (I get a password prompt in Win10.

Then why are you setting --ssh="ssh -p 5222"? Don't. The connection string ​ssh://user@fqdn:5222/100 already has the port number.

When you don't set --ssh=, you end up using the paramiko backend, which will prompt for passwords, etc. When you set --ssh=ssh, you end up using the openssh backend. Which you can debug by setting:

set XPRA_SSH_DEBUG=1

Before running xpra. It will then log the full command it will try to use. But I doubt that the openssh backend will work on MS Windows. Normally, the other backend on MS Windows is "plink.exe".

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #2577

    • Property Owner changed from Antoine Martin to akikoo
  • Ticket #2577 – Description

    initial v2  
    11This works starting up xpra on the remote:
    2 
     2{{{
    33ssh -p 5222 user@fqdn xpra start :100 --start=mate-terminal
    4 
     4}}}
    55This starts xpra on Win10 but doesn't ask for my ssh user password:
    6 
     6{{{
    77"\Program Files\Xpra\Xpra.exe" attach --ssh="ssh -p 5222" ssh://user@fqdn:5222/100
    8 
    9 The connection works if I leave out --ssh="ssh -p 5222" (I get a password prompt in Win10. Originally I needed to use --ssh="ssh -i" for ssh key setup.
     8}}}
     9The connection works if I leave out {{{--ssh="ssh -p 5222"}}} (I get a password prompt in Win10. Originally I needed to use --ssh="ssh -i" for ssh key setup.
    1010
    1111The systray icon in Win10 only has "Information" and "Close Menu" selectable. Other entries are greyed out.