2 ms·
Undetectable root kits. Which is a pretty serious problem, admittedly. It's an open question whether or not secured boot is a good or effective way to go about
by InclinedPlane 14y ago
Undetectable root kits. Which is a pretty serious problem, admittedly. It's an open question whether or not secured boot is a good or effective way to go about solving it.
- ajross 14y agoI'm not sure that you can call pre-kernel malware a "serious problem" yet. It exists, but is rare. Stuxnet and Flame seem to have the current crowns for "best malware" and did their deeds without it, after all. It's also important to point out that the secure code chain is also held up (albeit often incorrectly) as an important criteria for a working DRM implementation. The content providers like that story, and like to hear about efforts to prevent rogue code from running. Certainly this has a lot to do with the Intel/Microsoft rush to secure boot.
- InclinedPlane 14y agoIt's a serious problem when it happens, but it's not at all widespread. Though there's a good argument to be made that we shouldn't wait for problems to become widespread before fixing them, especially when they are as potentially damaging as rootkits. Imagine if we'd spent the 70s and 80s taking buffer overflow issues very seriously, for example. We'd live in a much different and arguably better world. The point still stands on whether or not this is actually the best or most effective way to go about tackling the problem. And as you point out the "unintended" of securing the DRM chain and of increasing vendor OS lock-in are not to be ignored and probably just as much a factor behind adoption as the purported security issues.