From thejunk.b at gmail.com Sun Feb 4 16:34:59 2018 From: thejunk.b at gmail.com (Randy) Date: Sun, 04 Feb 2018 11:34:59 -0500 Subject: [winswitch] xpra/winswitch on Raspberrypi Message-ID: <5345882.HBUBh4vgyl@bumblebee> Question If I add the winswitch debian/ubunto repo to my pi3 and install from there will it work correctly or do winswitch/xpra have to be compiled from source to work? Thanks -- If it ain't broke tweek it From antoine at nagafix.co.uk Mon Feb 5 02:48:39 2018 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 5 Feb 2018 09:48:39 +0700 Subject: [winswitch] xpra/winswitch on Raspberrypi In-Reply-To: <5345882.HBUBh4vgyl@bumblebee> References: <5345882.HBUBh4vgyl@bumblebee> Message-ID: <90e5e5dd-67d2-5115-07a8-4a8c48c7587c@nagafix.co.uk> On 04/02/18 23:34, Randy via shifter-users wrote: > Question > > If I add the winswitch debian/ubunto repo to my pi3 and install from there > will it work correctly or do winswitch/xpra have to be compiled from source to > work? There are no binary packages for ARM, yet. You will have to install from source, follow: https://xpra.org/trac/wiki/Building/Other You may or may not need to tweak a thing or two, these instructions have not been used in a long time. Feel free to edit the wiki. Cheers Antoine From antoine at nagafix.co.uk Mon Feb 5 15:13:22 2018 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 5 Feb 2018 22:13:22 +0700 Subject: [winswitch] [ANNOUNCE] Xpra 2.2.4: minor fixes Message-ID: Hi, This update fixes a fair number of minor issues, none of them critical, there is no urgency to update if you were not affected. Binaries are available for all platforms again, including MS Windows and Mac OS. Those include the usual minor library updates from upstream. Release notes: * fix lost connection when using bandwidth system tray menu * fix miscalculations in bandwidth congestion detection * fix bandwidth spikes with non-video fallback * fix video encoder setup errors with invalid size requests * fix x265 codec spurious logging * fix python3 OpenGL client wrongly using default values (slower) * fix handling of geometry constraints on MS Windows * fix unreliable unit tests (use relative time in sample data) * fix webcam forwarding errors in encoding selection * fix error in mmap setup error handling * fix shadow server startup error with Python 3 builds * fix NVENC informational message contents * fix NVENC support for memoryview uploads * fix session browser link from the launcher * fix launcher color error with GTK3 * disable webcam support in 32-bit MS Windows builds (broken library) * disable NVFBC zerocopy using CUDA buffers (pending further testing) * don't log exceptions that don't exist, re-use existing exception * always clean builds by default (MS Windows) Links: https://xpra.org/trac/wiki/Source https://xpra.org/trac/wiki/Download Cheers Antoine From varvello at yahoo.com Wed Feb 7 07:51:45 2018 From: varvello at yahoo.com (Davide Varvello) Date: Wed, 7 Feb 2018 07:51:45 +0000 (UTC) Subject: [winswitch] Issue with Window-Switch and OSX "High Sierra" References: <952800512.170109.1517989905962.ref@mail.yahoo.com> Message-ID: <952800512.170109.1517989905962@mail.yahoo.com> Hi Antoine I've an issue with Window-Switch and OSX "High Sierra", sometimes I can't quit winswitch. The version of Window-Switch is 0.12.20. I try quit it but probably it remains like a zombie, even if I force quit it it remains, there is no Window-Switch process running and when I want to power off my Mac Window-Switch prevents it (see attached image) It did not happen with "El Capitan". I also downloaded the latest version of Window-Switch (from here: http://winswitch.org/dists/osx/x86/ ? Window-Switch.dmg 2016-12-06 11:33) but unfortunately it does not start at all.Can you help me, please? ThanksDavide From antoine at nagafix.co.uk Thu Feb 8 12:36:53 2018 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 8 Feb 2018 19:36:53 +0700 Subject: [winswitch] Issue with Window-Switch and OSX "High Sierra" In-Reply-To: <952800512.170109.1517989905962@mail.yahoo.com> References: <952800512.170109.1517989905962.ref@mail.yahoo.com> <952800512.170109.1517989905962@mail.yahoo.com> Message-ID: <205a42f5-df81-def3-0665-42504cea4fee@nagafix.co.uk> On 07/02/18 14:51, Davide Varvello via shifter-users wrote: > Hi Antoine > I've an issue with Window-Switch and OSX "High Sierra", sometimes I can't quit winswitch. Can you try to run it with "--debug-mode" from a terminal and see where it gets stuck during shutdown? > The version of Window-Switch is 0.12.20. I try quit it but probably it remains like a zombie, even if I force quit it it remains, there is no Window-Switch process running and when I want to power off my Mac Window-Switch prevents it (see attached image) > It did not happen with "El Capitan". I also downloaded the latest version of Window-Switch (from here: http://winswitch.org/dists/osx/x86/ ? Window-Switch.dmg 2016-12-06 11:33) but unfortunately it does not start at all.Can you help me, please? Please try 0.12.22 if the 0.12.23 builds have problems. I have every version of Mac OS available to me in a VM, except for "High Sierra".. so I can't reproduce the problem, which makes it hard to fix. Setting up a new VM is on my todo list. Cheers Antoine > ThanksDavide > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From varvello at yahoo.com Thu Feb 8 16:47:45 2018 From: varvello at yahoo.com (Davide Varvello) Date: Thu, 8 Feb 2018 16:47:45 +0000 (UTC) Subject: [winswitch] Issue with Window-Switch and OSX "High Sierra" In-Reply-To: <205a42f5-df81-def3-0665-42504cea4fee@nagafix.co.uk> References: <952800512.170109.1517989905962.ref@mail.yahoo.com> <952800512.170109.1517989905962@mail.yahoo.com> <205a42f5-df81-def3-0665-42504cea4fee@nagafix.co.uk> Message-ID: <1697751420.1132186.1518108465608@mail.yahoo.com> Good, first I'll try with the debug mode, then with the 0.12.22,I'll feedback you next days CheersDavide From: Antoine Martin via shifter-users To: shifter-users at lists.devloop.org.uk Sent: Thursday, February 8, 2018 1:37 PM Subject: Re: [winswitch] Issue with Window-Switch and OSX "High Sierra" On 07/02/18 14:51, Davide Varvello via shifter-users wrote: > Hi Antoine > I've an issue with Window-Switch and OSX "High Sierra", sometimes I can't quit winswitch. Can you try to run it with "--debug-mode" from a terminal and see where it gets stuck during shutdown? > The version of Window-Switch is 0.12.20. I try quit it but probably it remains like a zombie, even if I force quit it it remains, there is no Window-Switch process running and when I want to power off my Mac Window-Switch prevents it (see attached image) > It did not happen with "El Capitan". I also downloaded the latest version of Window-Switch (from here: http://winswitch.org/dists/osx/x86/ ? Window-Switch.dmg 2016-12-06 11:33) but unfortunately it does not start at all.Can you help me, please? Please try 0.12.22 if the 0.12.23 builds have problems. I have every version of Mac OS available to me in a VM, except for "High Sierra".. so I can't reproduce the problem, which makes it hard to fix. Setting up a new VM is on my todo list. Cheers Antoine > ThanksDavide > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > _______________________________________________ shifter-users mailing list shifter-users at lists.devloop.org.uk http://lists.devloop.org.uk/mailman/listinfo/shifter-users From antoine at nagafix.co.uk Mon Feb 12 15:58:54 2018 From: antoine at nagafix.co.uk (Antoine Martin) Date: Mon, 12 Feb 2018 22:58:54 +0700 Subject: [winswitch] [ANNOUNCE] Xpra 1.0.10 LTS : many fixes, none critical Message-ID: <9fc4a56c-41f9-925a-1f47-7d45825cea2b@nagafix.co.uk> Hi, This update fixes many issues, but none of them are critical. Reminder: unless your systems are running CentOS 6.x or Windows XP, you should have moved to a newer release by now. In particular, the MS Windows and Mac OS builds are known to contain outdated libraries with security issues. Release notes: * fix crash with invalid tray docking requests * fix client authentication failures with multiple challenges * fix errors with some unauthenticated connections * fix system tray menu entries wrongly disabled * fix man page for all 'start' command variants * fix handling of encodings with uppercase characters (png/L and png/P) * fix error in server window debug logging * fix launcher error with informational command line exit messages * fix packet warnings with large "input-devices" packets * fix speed and quality not honoured initially * fix typo in file location example * fix compatibility with newer versions of python-lz4 * fix xauth file location * fix win32 MSI config build scripts * fix py2app packaging issues with missing gi bindings * fix rare server failure when some theme icons are missing * fix HTML5 client wrongly claiming to support system trays * fix RPM permissions on shared libraries * fix video encoder setup errors with invalid size requests * fix unreliable unit tests (use relative time in sample data) * disable webcam support in 32-bit MS Windows builds (broken library) * ffmpeg 3.5 compatibility * don't expose icon absolute paths to clients * add missing file to build clean list * remove invalid option from configuration file example Source: https://xpra.org/trac/wiki/Source Downloads: https://xpra.org/trac/wiki/Download Cheers Antoine From vfclists at gmail.com Mon Feb 12 18:20:42 2018 From: vfclists at gmail.com (vfclists .) Date: Mon, 12 Feb 2018 18:20:42 +0000 Subject: [winswitch] Is there a guide for configuring xpra to work as an Nginx proxy and SSL as well? Message-ID: I configure wetty , https://github.com/krishnasrinivas/wetty, to run behind an nginx frontend, and the nginx settings for running wetty as an upstream proxy looks like this. I also tried guacamole and the setting where similar. location /wetty { if ($scheme = 'http') { rewrite ^ https://$http_host$request_uri? permanent; } proxy_pass http://127.0.0.1:3111/wetty; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_read_timeout 43200000; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $http_host; proxy_set_header X-NginX-Proxy true; } I am not quite sure what a lot of the settings do, but it has worked well so far. My assumption is that if xpra uses has a '--bind-tcp=0.0.0.0:44440', the nginx proxy would have the 'proxy_pass http://127.0.0.1:44440'. I don't see the need to add an SSL option to the xpra command as nginx will be handling the SSL, but a password may be needed for the user, which has an option for it in the HHML interface Does anyone have a sample nginx config for xpra? Am I generally on the right path?. -- Frank Church ======================= http://devblog.brahmancreations.com From antoine at nagafix.co.uk Tue Feb 13 04:03:08 2018 From: antoine at nagafix.co.uk (Antoine Martin) Date: Tue, 13 Feb 2018 11:03:08 +0700 Subject: [winswitch] Is there a guide for configuring xpra to work as an Nginx proxy and SSL as well? In-Reply-To: References: Message-ID: <7bb7f559-3bed-deec-3ccc-76fff9b69e87@nagafix.co.uk> On 13/02/18 01:20, vfclists . via shifter-users wrote: > I configure wetty , https://github.com/krishnasrinivas/wetty, to run > behind an nginx frontend, and the nginx settings for running wetty as an > upstream proxy looks like this. I also tried guacamole and the setting > where similar. Then it's probably right. > location /wetty { > > if ($scheme = 'http') { > rewrite ^ https://$http_host$request_uri? permanent; > } > proxy_pass http://127.0.0.1:3111/wetty; > proxy_http_version 1.1; > proxy_set_header Upgrade $http_upgrade; > proxy_set_header Connection "upgrade"; > proxy_read_timeout 43200000; > > proxy_set_header X-Real-IP $remote_addr; > proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; > proxy_set_header Host $http_host; > proxy_set_header X-NginX-Proxy true; > } > > I am not quite sure what a lot of the settings do, but it has worked well > so far. > > My assumption is that if xpra uses has a '--bind-tcp=0.0.0.0:44440', the > nginx proxy would have the 'proxy_pass http://127.0.0.1:44440'. I don't see > the need to add an SSL option to the xpra command as nginx will be handling > the SSL, but a password may be needed for the user, which has an option for > it in the HHML interface The username and password are only needed if you configure xpra with authentication. If this is running in a secure environment, this may or may not be needed. Just be careful that one backend session can't connect to another for example. > Does anyone have a sample nginx config for xpra? I have never used an nginx proxy, but maybe someone else can chime in. Or maybe you can ask the nginx devs to confirm? > Am I generally on the right path?. I don't know. One word of warning though: xpra is very sensitive to latency and any piece of software sitting in between the client and the server will introduce some latency. For example, we've ended up incorporating the websockify server into the xpra server to reduce the websocket latency. If you can do it, always prefer direct connections. Cheers Antoine From ajs1 at cam.ac.uk Tue Feb 13 12:04:21 2018 From: ajs1 at cam.ac.uk (Anthony Stone) Date: Tue, 13 Feb 2018 12:04:21 +0000 Subject: [winswitch] xpra display problem Message-ID: <76fb8b05-96d6-b1f3-3cb1-6fac365bda57@cam.ac.uk> I'm running xpra 2.2.4 under Ubuntu 16.04 on both client and server. When I enter on the client xpra start ssh/whirligig --start=gnome-terminal to connect via an ssh tunnel (already set up) to the server on whirligig, I get the error Error: displayfd failed did not provide a display number using displayfd xpra initialization error: failed to identify the new server display! If instead I use xpra start ssh/whirligig/9 --start=gnome-terminal I get a session running on display 9, although it seems a bit flaky -- the display background colour keeps changing. The server system software is newly installed, so maybe some necessary package is missing. I had no trouble with a previous server setup under Ubuntu 14.04. Any suggestions gratefully received. Anthony From antoine at nagafix.co.uk Thu Feb 15 12:40:04 2018 From: antoine at nagafix.co.uk (Antoine Martin) Date: Thu, 15 Feb 2018 19:40:04 +0700 Subject: [winswitch] xpra display problem In-Reply-To: <76fb8b05-96d6-b1f3-3cb1-6fac365bda57@cam.ac.uk> References: <76fb8b05-96d6-b1f3-3cb1-6fac365bda57@cam.ac.uk> Message-ID: <2e51d2ad-81a8-644f-f8ef-60bcfba93818@nagafix.co.uk> On 13/02/18 19:04, Anthony Stone via shifter-users wrote: > I'm running xpra 2.2.4 under Ubuntu 16.04 on both client and server. > When I enter on the client > > xpra start ssh/whirligig --start=gnome-terminal > > to connect via an ssh tunnel (already set up) to the server on > whirligig, Have you tried the same thing without using an existing tunnel? It shouldn't make any difference, but it is worth a try. > I get the error > > Error: displayfd failed > did not provide a display number using displayfd > xpra initialization error: > failed to identify the new server display! It could be because Ubuntu 16.04 is the only distribution that is unable to use Xdummy. For more information see: https://xpra.org/trac/wiki/Xdummy I'll try to take a look, feel free to create a ticket for it so I don't forget, I did see the warning when I tried, but the session started OK anyway. > If instead I use > > xpra start ssh/whirligig/9 --start=gnome-terminal > > I get a session running on display 9, although it seems a bit flaky -- > the display background colour keeps changing. I don't see any problems here. This could be a problem with your opengl graphics drivers client side. Try switching opengl off. > The server system software is newly installed, so maybe some necessary > package is missing. That's unlikely. > I had no trouble with a previous server setup under > Ubuntu 14.04. This could be a regression in xpra. Ubuntu 14.04 uses xpra 1.x only. Cheers Antoine > > Any suggestions gratefully received. > > Anthony > > > _______________________________________________ > shifter-users mailing list > shifter-users at lists.devloop.org.uk > http://lists.devloop.org.uk/mailman/listinfo/shifter-users > From vfclists at gmail.com Thu Feb 15 19:11:24 2018 From: vfclists at gmail.com (vfclists .) Date: Thu, 15 Feb 2018 19:11:24 +0000 Subject: [winswitch] Authentication doesn't seem to work well Message-ID: The authentication methods like --auth=file and --auth=multifile don't seem work and I wonder if they work with the html options, or some of the options I use on the command line automatically nullify them? The only one that seemed to work was --auth=password option, but that only worked when stopping the server, rather than when making the connection. The 'xpra stop' command would prompt for it then. The version of xpra installed (on Debian Stretch) is 2.2.4-r18312-1 -- Frank Church ======================= http://devblog.brahmancreations.com From antoine at nagafix.co.uk Fri Feb 16 03:06:54 2018 From: antoine at nagafix.co.uk (Antoine Martin) Date: Fri, 16 Feb 2018 10:06:54 +0700 Subject: [winswitch] Authentication doesn't seem to work well In-Reply-To: References: Message-ID: On 16/02/18 02:11, vfclists . via shifter-users wrote: > The authentication methods like --auth=file and --auth=multifile don't > seem work and I wonder if they work with the html options, or some of the > options I use on the command line automatically nullify them?No "auth" is not meant to have any effect on sockets other than unix domain sockets. See --tcp-auth, --ssl-auth, --ws-auth and --wss-auth for the authentication of other socket types, bearing in mind that a tcp socket can be upgraded to an ssl or ws(s) socket. BTW, nowadays sqlite is preferred over multifile. > The only one that seemed to work was --auth=password option, but that only > worked when stopping the server, rather than when making the connection. > The 'xpra stop' command would prompt for it then. That's working as intended. Usually the unix domain socket is left unauthenticated ("--auth=none") as it is already protected by unix file permissions. > The version of xpra installed (on Debian Stretch) is 2.2.4-r18312-1 > Cheers Antoine From vfclists at gmail.com Fri Feb 16 14:32:59 2018 From: vfclists at gmail.com (vfclists .) Date: Fri, 16 Feb 2018 14:32:59 +0000 Subject: [winswitch] How to create a reverse and SSL proxy for xpra. Message-ID: I want to create a reverse and SSL proxy for xpra - https://xpra.org/, a remote desktop facility for X windows, like x2go and VNC. The proxy is targeted at the HTML5 option which allows the info to be transferred via websockets. The way to connect directly to an xpra HTML5 server is to enter the address and the port directly to the browser eg. http://1.2.3.4:5000. A page appears prompting for the target server and port, login credentials and a few others, and when filled properly the desktop comes up. This is my first attempt to create an nginx proxy from scratch and I have already hit a snag. My aim is to have different locations connecting to server:port connections, so I have something like this location /xpra { proxy_pass http://111.222.213.221:14003; # proxy_pass http://127.0.0.1:14003; proxy_http_version 1.1; proxy_buffering off; } proxy_pass is the main option whose relevance I have checkied, the other two are options which seem to useful. Whenever i try to open a page http//:111.222.111.221/xpra, the following results Error response Error code 404. Message: File not found. Error code explanation: 404 = Nothing matches the given URI. ================= The code for the client is at - https://xpra.org/html5/connect.html -- Frank Church ======================= http://devblog.brahmancreations.com From vfclists at gmail.com Sat Feb 17 13:06:16 2018 From: vfclists at gmail.com (vfclists .) Date: Sat, 17 Feb 2018 13:06:16 +0000 Subject: [winswitch] What is the proper format the password files? Message-ID: I created a username/password combination of the form onetwo:bucklemyshoe, ie the password file contains the single line 'onetwo|bucklemyshoe' Whenever I try to connect the message appears on the logon page: You were disconnected for the following reason: invalid challenge response The logs display the following message Authentication required by password file authenticator module sending challenge for username 'onetwo' using hmac+sha256 digest Warning: hmac+sha256 challenge for 'onetwo' does not match Warning: authentication failed invalid challenge response Disconnecting client Protocol(ws websocket: 111.111.111.111:14333 <- 222.222.222.222:35555): invalid challenge response It makes no difference whether ' Insecure plain-text passwords' is checked or not. The contents of the password file is not what xpra expects. Is the actual format documented somewhere? Is there an utility or script to create them in the right format? -- Frank Church ======================= http://devblog.brahmancreations.com From antoine at nagafix.co.uk Sat Feb 17 14:08:31 2018 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sat, 17 Feb 2018 21:08:31 +0700 Subject: [winswitch] What is the proper format the password files? In-Reply-To: References: Message-ID: <2baa1d29-8215-f2bc-9032-a3392a9da5d7@nagafix.co.uk> On 17/02/18 20:06, vfclists . via shifter-users wrote: > I created a username/password combination of the form onetwo:bucklemyshoe, > ie the password file contains the single line 'onetwo|bucklemyshoe' > > Whenever I try to connect the message appears on the logon page: > > You were disconnected for the following reason: > > invalid challenge response > The logs display the following message > > Authentication required by password file authenticator module > sending challenge for username 'onetwo' using hmac+sha256 digest > Warning: hmac+sha256 challenge for 'onetwo' does not match > Warning: authentication failed > invalid challenge response > Disconnecting client Protocol(ws websocket: 111.111.111.111:14333 <- > 222.222.222.222:35555): > invalid challenge response > > It makes no difference whether ' Insecure plain-text passwords' is checked > or not. > > The contents of the password file is not what xpra expects. Is the actual > format documented somewhere? https://xpra.org/trac/wiki/Authentication > Is there an utility or script to create them > in the right format?No tool needed: echo -n "bucklemyshoe" > yourpasswordfile.txt Cheers Antoine From antoine at nagafix.co.uk Sun Feb 18 03:24:49 2018 From: antoine at nagafix.co.uk (Antoine Martin) Date: Sun, 18 Feb 2018 10:24:49 +0700 Subject: [winswitch] What is the proper format the password files? In-Reply-To: References: <2baa1d29-8215-f2bc-9032-a3392a9da5d7@nagafix.co.uk> Message-ID: (..) Please don't bottom post, and please always keep the mailing list CCed. > > The contents of the password file is not what xpra expects. Is the actual > > format documented somewhere? > https://xpra.org/trac/wiki/Authentication > > > Is there an utility or script to create them > > in the right format?No tool needed: > echo -n "bucklemyshoe" > yourpasswordfile.txt > > How about the one that contains username and password combinations, ie > ?-|-auth=multifile:filename=/path/to/userlist.txt| The format is described in the man page and on the wiki. As per a previous reply, the sqlite backend is easier to use and provides command line tools to set things up. That's assuming that you need to allow multiple username+password pairs. If not, then "file" authentication is much easier to manage. > I assume that userlist.txt contains username, password and a few other > values besides, > and that username and password are encoded, ie not in plaintext. This file is also plain text, same as the "file" authentication module. The same answer applies here, please read the links I've already posted to understand why that is. > PS. I tried the pam option, which logs the person straight into the > desktop from the webpage, pam does no such thing. pam is an authentication module which is configured to check the local password database. The session xpra connects to is orthogonal to the authentication module used. You will get logged in to a "desktop" using "shadow" or "start-desktop" subcommands only. > but I would rather not do it that way as I explain at > https://unix.stackexchange.com/questions/424797, > because I prefer? multiple layers of security Then you should consider SSL or SSH as transports. You can now also stack multiple authentication modules in 2.3: https://xpra.org/trac/ticket/1728 Cheers Antoine PS: please don't re-open tickets unless the issue is not resolved / still requires work.