3 ms·
"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 exa
by makomk 10y ago
"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.
- pjmlp 10y agoYes, http://arstechnica.com/security/2016/09/linux-kernel-security-needs-fixing/2/ 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.
- scarybeast 10y agoYou are clairvoyant :) I'm working on this area. Some distros have this problem with their default Gnome-based desktops too.