zlacker

[return to "Pluton is not currently a threat to software freedom"]
1. messe+sa[view] [source] 2022-01-09 03:37:29
>>foodst+(OP)
The fearmongering about Pluton feels very similar to the criticism that was levied against UEFI Secure Boot when it was being debuted. In the end, x86 systems didn't become any more locked down.

I predict that this will blow over, and won't be a big deal in a few years time once FOSS drivers for what is effectively just a new breed of TPM are released.

If in five years, it turns out I was wrong, I'll eat my hat. Although defining "my hat" by then might be difficult, as it'll probably be subscription based.

◧◩
2. userbi+Mb[view] [source] 2022-01-09 03:48:28
>>messe+sa
In the end, x86 systems didn't become any more locked down.

Oh hell yes they did. Look at Intel Boot Guard and all the stuff around that.

◧◩◪
3. gruez+Nc[view] [source] 2022-01-09 03:57:46
>>userbi+Mb
>Look at Intel Boot Guard and all the stuff around that.

what am I looking for? It looks like you couldn't load third party/modified firmware with that enabled? I suppose it's strictly more locked down than being able to flash whatever firmware you want, but was there a sprawling scene of modified firmware around at that time? Or did everybody essentially run the stock firmware?

◧◩◪◨
4. userbi+Ve[view] [source] 2022-01-09 04:16:43
>>gruez+Nc
BIOS mods are not exactly common, but there's plenty of people doing it. Projects like coreboot are another example, and of course all the tools around removing as much of the ME as possible. Obviously the "fringe" gets slowly trimmed, and we should be looking out for those like we do canaries in a coalmine.
◧◩◪◨⬒
5. gruez+5h[view] [source] 2022-01-09 04:36:49
>>userbi+Ve
I'm not exactly sure how me_cleaner works, but AFAIK it still works even with intel bootguard? I believe the way it works is that intel ME are present in the bios as optional modules, and they can be removed without messing up the signature.
[go to top]