[winswitch] Windiws client usage (was: Re: BUG: Mouse pointer stops working in multi-/single display setup)
lukashaase at gmx.at
Wed Nov 26 10:53:29 GMT 2014
Sorry, I need to add something ...
> Hi Antoine,
> >> [...]
> >> I used GSSAPI authentication first and needed to pass certain options to plink. I didn't see how this works with
> >> winswitch/xpra. (Is it possible? Particularly, supplying a session name or SSH public key would be interesting)
> > I am not at all sure how well this works with plink and command line arguments, but this is what the "--ssh=" flag is for.
> > [...]
> I played around with this; indeed, the *.xpra file accepts a ssh= line.
> However, it seems to me that arguments are parsed improperly.
> When I use
> ssh="plink.exe -noagent -i o:\pkey.ppk"
> I get:
> Error running ssh program '[plink.exe -noagent -i o:\pkey.ppk', '-l', 'lukas', '-ssh'....
> [Error 2] The system cannot find the file specified
> It seems that in this case, the complete command is interpreted as executeable which can of course indeed not be found.
> When I use (without quotes)
> ssh=plink.exe -noagent -i o:\pkey.ppk
> then the appended arguments seem to be dropped; in any case they are ignored.
> Independently from that, I see that xpra itself supplies "-agent" to plinks argument list. This might not be always wanted, for example in my case.
> Therefore I would suggest to add a "ssh_args" option if it can be easily implemented.
> If this is not set, do whatever is done now (with "ssh" executeable).
> If this is set, these arguments are passed to "ssh", along with "-l username" and the command to be executed but otherwise no "default" arguments such as "-agent".
> This method would also allow to pass "-load mysession" and hence GSSAPI authentication would work :-)
Actually it seems that the command is parsed correctly but exactly what is done above is the problem - I pass "-noagent -i file" and xpra additionally passes "-agent". Therefore the agent is queried although I explicitely supply "noagent".
The reason is that this might indeed not be always wanted. In my case, I use a "special" agent which is most of the time locked and I get a password dialog on a key request. In case of xpra, it just hangs until I enter the master password. I use this agent for conventional SSH login systems. However, when SSH is used for automated things (scripts or xpra in this case) the agent should not be queried but an explicit SSH key is supplied.
The proposal with "ssh_arg" would fix scenarios like these.
More information about the shifter-users