00:07 <michael> my other problem is that the client is bigendian and it seems that wayland rejects clents that have different endiness by default. Googling it seems that there may be an option for wayland "+byteswappedclients" to allow this (as there is now in Xserver) but it's notr mentioned in the man page. Is this a real option to Xwayland?

00:09 <DemiMarie> michael: Yes, and I strongly recommend you use a VM and dedicated NIC for the old hardware.

00:10 <DemiMarie> * I believe so, as server-side byte-swapping has turned out-of-bounds reads into out-of-bounds writes (and thus code execution) in the past. That said, I strongly recommend using rootful Xwayland for this, or (even better) a dedicated VM. Performance for such old clients won’t matter.

00:10 <michael> ..mmm OK, then I must have another issue that's causing it to fail 8-(

00:11 <DemiMarie> Rootless Xwayland with no authentication allows anyone who can connect to your server to take control of your session and any X11 programs in it. Using a dedicated rootful Xwayland instance mitigates this to some degree.

00:11 <DemiMarie> I also recommend using a dedicated network card to connect to the device and disabling routing between it and the outside world.

00:12 <michael> Yes, this is an entirely internal system and the ethernet is just conmnected to the lab instruments

00:22 <whot> michael: options in Xserver are common to all implementations, including Xorg and Xwayland

00:22 <whot> so man Xorg and man Xwayland only show you the options that others don't support

00:33 <michael> OK ... "-listen tcp" did not work but the "socat" trick did!! (and the +byteswappedclients did also). As suggested I had to make a shell version of Xwayland to add the command line option. Is there a method of getting the "+byteswappedclients" other than in the command line?

01:01 <whot> not for xwayland, no

01:02 <michael> ok

01:05 <danieldg> this is because X has previously had a number of security vulnerabilities from byte-swapped clients

01:05 <danieldg> they decided to just disable that rather than fixing the problem

03:30 <soreau> zamundaaa: I was thinking that if the blur protocol is basically designed to define the contents behind a surface, it could be expanded to also request the 'desktop background image' instead of whatever is stacked behind it, blurred or not. However, it seems like this would warrant a protocol name change. (surface-backing?) Do you guys already offer a way to use the background image instead of whatever might be stacked behind it?

03:44 <DemiMarie> danieldg: I think they will still fix any problems that are found, but they also wanted to significantly reduce attack surface.

07:56 <whot> yeah, we'll fix what comes up but meanwhile not exposing every X server running to those bugs seemed like a good idea :)

11:36 <zamundaaa[m]> soreau: renaming it to be nicer to extend later sounds fine to me

11:37 <zamundaaa[m]> "ext-backdrop-effect" would be fitting I think

11:38 <zamundaaa[m]> Or just ext-background-effect

11:40 <zamundaaa[m]> As for the wallpaper question, no we don't have that yet. I did want to experiment with it as a replacement for the normal blur effect for lower end hardware, but that doesn't really need clients to know or care

11:43 <soreau> I was thinking some might want the desktop background but also blurred.. I've had users ask for a blur protocol but just about as many have asked for the desktop background instead

11:44 <soreau> so maybe a switch for either 'stacked' or 'desktop' contents, and the blur stuff could be applied to either

11:45 <soreau> then for lower grade hw where blur might choke, could just ignore client preference for blur and use whatever 'background contents' the client etched out

11:46 <soreau> the only question I might wonder is, can a client request some portions be 'stacked' and another portion be 'desktop' in the same surface

11:47 <soreau> seems like it should be only one or the other, not supporting both (for the same surfce)

11:50 <soreau> but it still feels like clients meddling in decisions for the composition might make the desktop appear messy, if not done carefully to make it tasteful :P