4 ms·
If they are sane, Intel didn't rely on this staying secret in their threat model.
by fulafel 4y ago
If they are sane, Intel didn't rely on this staying secret in their threat model.
- jacquesm 4y agoIf they were truly sane this whole thing would have never existed, so all bets are off on that one.
- mjg59 4y agoDepending on how microcode is defined, it's arguably existed back to the 40s. Which modern and reasonably performant CPUs are you thinking of that don't have microcode?
- jacquesm 4y agoYou completely misunderstood my comment.
- mjg59 4y agoWhat were you referring to, other than microcode? Edit: Oh, you mention the encryption. Big companies love obfuscating everything they create, because they're afraid something commercially sensitive will exist there and someone will copy it and outcompete them. I agree that this is ridiculous, but I don't think it's evidence of any sort of nefarious activity.
- jacquesm 4y agoIt's not evidence, but it may well have been used to hide such evidence.
- mjg59 4y agoWell yes anything that's encrypted could potentially turn out to be evidence of a crime when decrypted, but we don't usually assume that the use of encryption is indicative of that
- sroussey 4y agoMicrocode spills lots of the secrets of the hardware design, so you want it encrypted for as many years as possible to keep your trade secrets out of competitors’ hands.
- jpgvm 4y agoThey were always going to need microcode to deal with errata or are you referring to encrypting the microcode rather than just signing it?
- jacquesm 4y agoThe latter. I can see why they did it but if it was used to hide something nefarious Intel is done.
- ta988 4y agoIf they have to hide something, it will not be in the microcode. They always expected it to be broken one day. If it is on the die it will take a massive effort to be found and understood, if ever. And it is actually much easier to hide from the employees as if it was in the microcode, many of them could have extracted the keys and sold them to a foreign power.
- masklinn 4y agoWhat whole thing? Instruction microcoding is nothing new. Or do you mean. - the TXE vulnerability and / or undocumented debugging mode (so microcode wouldn’t have been extracted) - microcode encryption so the microcode would always have been completely readable - x86 - Intel itself ?
- jacquesm 4y agoThe second, possibly combined with something dirty. I can see why they would sign/encrypt it so that things got safer, but then they should have done a much better job of it. If it was encrypted to hide something that could not stand the light of day then that's an entirely different matter altogether. Time will tell.
- hansendc 4y agoFrom: https://arstechnica.com/gadgets/2020/10/in-a-first-researchers-extract-secret-key-used-to-encrypt-intel-cpu-code/ https://arstechnica.com/gadgets/2020/10/in-a-first-researche... "In a statement, Intel officials wrote: ... we do not rely on obfuscation of information behind red unlock as a security measure." (BTW, I work on Linux at Intel, I'm not posting this in any official capacity)
- marcodiego 4y ago> I work on Linux at Intel, I'm not posting this in any official capacity Oh, great! Isn't there a way where intel could provide keys so we could get rid of IME even if it means we won't be able to play DRM'ed content?
- sabas123 4y agoIIRC IME also does a lot of core functionality like power regulation. Unlike many in this thread probably think, it does provide a lot of core functionality that you probably don't want removed.
- bogomipz 4y agoInteresting. So IME handles dynamic voltage and frequency scaling(DVFS) or cores then?
- ta988 4y agoThermal management, power gating, scheduling... It does a lot.
- salawat 4y agoThe contention, from the User standpoint, however, is the network stack, potential to phone home, and the unrestricted access to the global machine state, combined with the fact, it is not documented or disclosed. It's one thing to have that and be up front and open on it. Get secretive, and you're creating a massive source of unknown unknowns for everyone involved. And like it or not, if you won't/can't be transparent about it, either A) It'd take too long to document, which suggests there may be room for simplification B) you're doing something that if it saw the light of day, would cause outrage, likely because you shouldn't be doing it C) You're holding back the state-of-the-art for the sake of securing a revenue stream. None of these inspires a excess of confidence/trust.