3 ms·
It's an old post, but it applies to X.org all the same. Wasn't Wayland planning on addressing these issues?
by shmerl 13y ago
It's an old post, but it applies to X.org all the same. Wasn't Wayland planning on addressing these issues?
- ape4 13y agoHere's some guy getting xeyes working on Wayland. http://blogs.gnome.org/wjjt/2012/03/14/looking-around-wayland/ http://blogs.gnome.org/wjjt/2012/03/14/looking-around-waylan...
- EmanueleAina 13y agoThat proof-of-concept relied on a custom protocol extension which, as the author pointed out, was not meant to be merged in Wayland/Weston. In any case the extension required application to ask the compositor to be notified of the pointer position even when not "owning" it and the compositor can flatly refuse it to non-privileged clients according to any policy it wants, which is quite different from the current X11 situation. This article has some useful information on how Wayland addresses the security concerns expressed in this thread: http://mupuf.org/blog/2014/02/19/wayland-compositors-why-and-how-to-handle/ http://mupuf.org/blog/2014/02/19/wayland-compositors-why-and...
- edwintorok 13y agoHere's a summary of security in Wayland: http://mupuf.org/blog/2014/02/19/wayland-compositors-why-and-how-to-handle/ http://mupuf.org/blog/2014/02/19/wayland-compositors-why-and... https://lwn.net/Articles/589147/ https://lwn.net/Articles/589147/