News for hackers. Stuff that matters.
Re:The Linux graphics stack from X to Wayland (2011) by bandrami on Monday September 19, 2016 @10:17AM (#12531614)
Yes and no. Wayland protects from userspace keyloggers after libevent gets its hands on a keystroke. (For that matter, it also doesn't protect against screenscrapers that simply look at video memory.)
Re:The Linux graphics stack from X to Wayland (2011) by zokier on Monday September 19, 2016 @12:33PM (#12532667)
Doesn't exploiting both of those require root privileges? Protecting against malicious code running as root seems like a lost cause anyways..
Re:The Linux graphics stack from X to Wayland (2011) by nixos on Monday September 19, 2016 @01:05PM (#12532902)
Once you have regular user access, root is easy:

http://security.stackexchange.com/questions/119410/why-shoul...

Re:The Linux graphics stack from X to Wayland (2011) by zokier on Monday September 19, 2016 @01:45PM (#12533203)
Funny you should bring that up, I was thinking the other day that Wayland should be usable building block for "secure desktop" style thing, that would help to prevent many (if not all) of the vectors presented at your link.

Admittedly I haven't studied this in detail, so maybe there are some fatal aspects in Wayland that would make my ideas infeasible, but I hope that one day we could have more secure desktop privilege authorization.

Re:The Linux graphics stack from X to Wayland (2011) by bandrami on Monday September 19, 2016 @12:57PM (#12532829)
In a system that doesn't use capabilities, generally yes (though, again, even simply with group ownership of devices you can do a lot of stuff that in traditional configurations requires root). But capabilities have managed to sneak into everything nowadays.