4 ms·
Due to how XWayland works, a lot of applications (sometimes critical ones) won't work under XWayland ever (pretty much everything that works on interaction betw
by p_l 6y ago
Due to how XWayland works, a lot of applications (sometimes critical ones) won't work under XWayland ever (pretty much everything that works on interaction between X clients fails hard).
- phkahler 6y ago>> pretty much everything that works on interaction between X clients fails hard It's supposed to fail hard. That isnt just a security hole in X, it's a total lack of security. The notion that any app should be able to monitor or manipulate any other app is archaic and wrong from a security perspective.
- enriquto 6y agoThere they go htop, netcat, kill, and the whole unix pipe system. No, thanks. Programs monitoring other programs is the very essence of computing for us greybeards, and you will take this from our cold, dead hands!
- krageon 6y agoMaybe it's archaic and wrong to you. Maybe it's even a good idea to be able to configure this on a per-application basis. What isn't the case is that you get to know what is convenient and right in my workflow.
- phkahler 6y agoFair point. I think not allowing by default and having some means to grant permission is a decent idea, but implementation has to be right so people dont develop a habit of allowing it every time they're asked.
- account42 6y ago> That isnt just a security hole in X, it's a total lack of security. That "security" is useless on a Desktop where you run all programs as the same user. If you want a platform to run locked down "apps" that's fine, just don't expect others to be happy with the cost of that "security" when it provides no benefit for them.
- anthk 6y agoExactly. Also, XTerm has a secure mode where the keyboard input is locked and no application can read from it ever.