3 ms·
And yet, 12 years later, Wayland still has significant problems, and has not displaced X11. There's a reason for that: it's just not good enough. I find it ha
by kelnos 4y ago
And yet, 12 years later, Wayland still has significant problems, and has not displaced X11. There's a reason for that: it's just not good enough.
I find it hard to believe that the security issues with X11 could not be fixed. It might have to be done in a way that causes some incompatibilities and pain, but I can't imagine that would be anywhere near as bad as all the time people have spent working on and dealing with Wayland.
I mean, c'mon, here's a simple X11 "any app can read out the contents of any other window" solution: add access controls to Xorg so that they can't. You open a connection to the X server, and you can read any window created by that connection, and that's it. Input events? You only get the input events destined for windows created on your connection. Want to write a screenshot or screen recording app, or an app that allows sharing your screen? Cool, we can create an interface for that, one that requires user confirmation. Privilege separation is hardly an unsolved problem.
I'm not saying all of this is easy, but it strains credibility to suggest that this could not have been accomplished in the past 12+ years since work started on Wayland.
- pcwalton 4y ago> I mean, c'mon, here's a simple X11 "any app can read out the contents of any other window" solution: add access controls to Xorg so that they can't. This exists and is called XSECURITY. It breaks everything, so nobody uses it. Also, nobody thinks Xorg is secure against RCE from hostile clients: the code is just too old and brittle.
- uecker 4y agoXorg network code is considered well audited and very few problems have been found over the years. Please stop making stuff up.
- tadfisher 4y agoThe most recent release had to be rolled back after four zero-day remote privilege escalations were found and given CVEs. The network code may be fine, but everything exposed to the network is not, and manpower is dwindling to address problems.
- pcwalton 4y agoHere are a zillion memory safety problems in X libraries typical of what happens when you point a fuzzer at 1980s code: https://lists.x.org/archives/xorg-devel/2013-May/036276.html https://lists.x.org/archives/xorg-devel/2013-May/036276.html
- kaba0 4y agoWhy do you think you know enough on the topic to have such strong claims? Wouldn’t giving the benefit of the doubt to the developers behind Wayland (who came from X by the way) be the sane thing to do?