News for hackers. Stuff that matters.
Re:Compromising a Linux desktop using 6502 opcodes on the NES by makomk on Monday November 14, 2016 @02:12PM (#12952409)
"The attack surface of the Linux desktop does not appear to be under control, or adequately monitored for regression." No kidding. I ran into an interesting example for this a year or so back - the library used by KDE's search indexer for reading image metadata added support for video files with a bunch of classic buffer overflows in the new code, and even though it wasn't used to index video files a similar filename trick could be used to get the indexer to call it. Not sure how easy it would be to get code execution, but it wouldn't require any user interaction thanks to Google Chrome.
Re:Compromising a Linux desktop using 6502 opcodes on the NES by pjmlp on Monday November 14, 2016 @03:17PM (#12952927)
Yes,

http://arstechnica.com/security/2016/09/linux-kernel-securit...

This is probably the only reason I can somehow understand Google's draconian approach to the NDK APIs, versus what iOS and UWP allow for.

Re:Compromising a Linux desktop using 6502 opcodes on the NES by scarybeast on Monday November 14, 2016 @06:41PM (#12954357)
You are clairvoyant :) I'm working on this area. Some distros have this problem with their default Gnome-based desktops too.