Can't say I'm surprised that Matthew Garrett is the one who submitted this patch, considering that he's been involved in pushing ""trusted"" computing poison like this for at least the last decade (and is seemingly one of the only people in the industry that's even paid attention to Pluton's existence, really makes you think), and yet somehow I'm still disappointed; is this going to be a total catastrophe even though he claims he's only working on supporting the TPM implementation and not any of the weird remote attestation crap we still don't really know much about? Probably not. Could this also potentially lead to Pluton eventually being fully supported by the Linux kernel and Microsoft gaining untold amounts of control over an OS that they've already compromised to some extent? Maybe. All I know is that this deserves to be condemned either way and that the sooner Pluton dies off, the better. To be fair, Garrett claimed around a year ago that the disabling mechanisms in AMD's Pluton implementation are "probably good enough", but after the last decade+ of CPU black boxes and countless Microsoft screwups, "probably" is about as reassuring to me as saying that a pack of rabid, hungry wolves staring at you through the window "probably" won't break in and tear your face off while you're asleep tonight.
I remember Dave Weston claiming on Twitter that Pluton would be open sourced and fully supported by Linux sooner or later - was he counting on someone else doing the work for him? :^)
I remember Dave Weston claiming on Twitter that Pluton would be open sourced and fully supported by Linux sooner or later - was he counting on someone else doing the work for him? :^)
Comment