HNHacker News
TopNewBestAskShowJobs

totaam

4 karma · joined July 5, 2018

submissionscomments
totaam··on Xpra: Persistent Remote Applications for X11
Perhaps your users don't have the same abilities with ssh? The reason why xpra switched to paramiko as default ssh implementation is because it makes it possible to integrate (cross platform too) with the GUI so that asking for passphrases or passwords can be handled by the xpra process itself (it may already have the password or it may delegate to pinentry or gpg agent or putty agent or whatever). This also means that ssh errors can be handled much more gracefully - natively in the code. With openssh launched as a subprocess, the user interface is non-existent, and when the ssh process fails, all the xpra process sees is a dead process with a non-zero exit code - which is much more difficult to handle gracefully.
totaam··on Xpra: Persistent Remote Applications for X11
Apart from the SSH connection? The short answer is (probably) very little, the long answer is more complicated: https://github.com/Xpra-org/xpra/blob/master/docs/Usage/Secu...
totaam··on Xpra: Persistent Remote Applications for X11
If you don't want to change the global defaults (in `/etc/xpra`), or your personal config (`~/.config/xpra`), you should be able to stick `ssh=ssh` in a `$HOST.xpra` session file and the launcher should honour it when you open the file / double-click on it. (add `autoconnect=true` and the launcher won't be seen unless the connection fails)
totaam··on Xpra: Persistent Remote Applications for X11
No, the subcommand does not need to be the first arg.
totaam··on Xpra: Persistent Remote Applications for X11
You're making it way more complicated than it should be. Just edit the defaults in `/etc/xpra/conf.d/40_client.conf`: https://github.com/Xpra-org/xpra/blob/eedf34ecef3a04d0867709... (or your personal defaults in `~/.config/xpra`)