4 ms·
I always found that worry quite weird, these are processors that already have things like System Management Mode that takes control away from the kernel and run
by kryptiskt 7y ago
I always found that worry quite weird, these are processors that already have things like System Management Mode that takes control away from the kernel and runs some unknown code at an arbitrary point in the execution. Worrying about a subverted RNG and trusting the rest of the CPU will just create a load of busywork that does nothing to keep you more secure.
- zozbot234 7y agoSystem Management Mode is the feature that does things like getting your fans to spin up when the processor runs hot. Pretty critical when you put it like that. Yes, that requires "tak[ing] control away from the kernel and running some unknown code at an arbitrary point in the execution". We could do away with such things entirely, but then our kernels would look like coreboot code, and a comparatively trivial kernel bug could permabrick your system. Not a very sensible tradeoff!
- thenewnewguy 7y agoI think they're more worried about the untrusted/unauditable part of it. I suspect most people that dislike the ME would be perfectly fine with it if Intel released the code for it and allowed users to build and upload their own copy of the ME code.
- Dylan16807 7y agoIt could do that without having access to main memory or network chips!
- throwaway2048 7y agoA CPU executing arbitrary code that you didn't load is much, much easier to detect, than an RNG that looks random, but isn't. We already know that parties like the NSA have intentionally backdoored RNGs that made it into production use.
- paulmd 7y agoCPUs have been executing arbitrary code that you didn't load for more than a decade now. All Intel CPUs run a ring -3 supervisor core based on Minix, on AMD it's based on ARM TrustZone. If those supervisor cores want, they can literally just tamper with the entropy in your pool directly, they don't need to go through the charade of feeding it tampered entropy and then trying to un-mix it later.
- throwaway2048 7y agoThat is extremely prone to breaking, and could be trivially detected if somebody was looking for it. It is far less risky detection wise to just tamper with the RNG directly.
- altfredd 7y ago> If those supervisor cores want, they can literally just tamper with the entropy in your pool directly Go ahead and try to tamper with that pool. On all existing and future kernel versions. After undoing kASLR. Not arguing, that it is impossible, but malware writers usually choose easier paths. When Samsung backdoored their phones [1], they didn't make a pure TrustZone rootkit. Instead they created a companion app, acting as helper for performing high-level tasks within OS bounds. Intel ME rootkit has it's own network stack and can use Intel network card, because it is both easier and safer than trying to interact with constantly updating OS, written by different people. A rootkit, trying to perform any kind of complex interactions with host OS, may be exploited and taken advantage of, — for example see bugs [2] in AMD's PSP, that allowed host OS to take over by giving it specially crafted certificate. [1]: https://www.zdnet.com/article/backdoor-in-samsung-galaxy-devices-allows-remote-access-to-data/ https://www.zdnet.com/article/backdoor-in-samsung-galaxy-dev... [2]: https://seclists.org/fulldisclosure/2018/Jan/12 https://seclists.org/fulldisclosure/2018/Jan/12