[winswitch] xpra using cygwin ssh
antoine at nagafix.co.uk
Tue Apr 23 15:20:00 BST 2013
On 04/23/2013 09:08 PM, kristof.ralovich at gmail.com wrote:
> Dear All,
> I'm using xpra with great satisfaction. Recently I bumped into a issue
> while trying to attach to a server from a client behind a proxy. I've set
> up cygwin, ssh and connect-proxy to work hand-in-hand, for command line
> communication this pipeline is functional. Now, I would also like to use
> this working ssh setup for xpra too. To this end, I've changed this line
> ssh = c:/cygwin/bin/ssh.exe
> in c:\Program Files (x86)\Xpra\xpra.conf to point ssh to cygwin's.
You should be modifying the user's xpra.conf rather than the system
default, creating one if it doesn't exist.
IIRC, on win32 this would be %APPDATA%\Xpra\xpra.conf
This way it won't get overwritten with every Xpra software update.
> running Xpra_cmd.exe from a cygwin shell produced the output below:
> user at laptop /cygdrive/c/Program Files (x86)/Xpra
> $ ./Xpra_cmd.exe attach ssh:user at example.com:1001
> ** Message: pygobject_register_sinkfunc is deprecated (GstObject)
> xpra client version 0.8.8
> cannot read using ['c:/cygwin/bin/ssh.exe', '-l', 'user', '-T', 'example.com',
> '-ssh', '-agent', '.xpra/run-xpra', '--socket-dir=~/.xpra', '_proxy',
> ':1001']: the SSH process has terminated with exit code=255
> 2013-04-23 15:03:08,441 connection closed after 0 packets received (0
> bytes) and 0 packets sent (0 bytes)
> Exception in thread format (most likely raised during interpreter shutdown):
> Is there a way to print the output of ssh for debugging? Or any hints that
> I should consider?
On win32 we don't use putty.exe but plink.exe (and not the one from
putty, but the one from tortoise to get a GUI for accepting host keys
and asking for passwords).
The connection stage is too early to get any meaningful debugging
information using the "xpra -d all" flag I think.
Have you tried running that ssh command line by hand to make sure it
does work? I'm pretty sure it won't because it assumes that we're
dealing with "plink.exe" on win32, so the flags "-ssh" and "-agent" are
probably causing ssh.exe to abort with an error.
If the patch below works for you, I guess I could use the "ssh" syntax
when the ssh command looks like a proper ssh... ugly, but that's win32
### Eclipse Workspace Patch 1.0
--- src/xpra/scripts/main.py (revision 3132)
+++ src/xpra/scripts/main.py (working copy)
@@ -531,7 +531,7 @@
dtype = display_desc["type"]
if dtype == "ssh":
cmd = display_desc["full_ssh"]
- if sys.platform.startswith("win"):
+ if False:
password = display_desc.get("password")
cmd += ["-pw", password]
More information about the shifter-users