Re:Linux and TPMs with systemd measured boot [video]
by Nextgrid on Sunday November 05, 2023 @07:23PM
(#38157276)
> Windows already limits drivers to ones signed by Microsoft
I don't believe driver signature enforcement restricts what the driver can do, intentionally or as a result of a vulnerability. Maybe your driver intentionally allows user access to privileged kernel memory, or has a vulnerability that allows the same? Also, signing keys leak every so often.
Re:Linux and TPMs with systemd measured boot [video]
by mjg59 on Sunday November 05, 2023 @07:32PM
(#38157336)
Microsoft has signed drivers that allow you to modify arbitrary kernel code, so.
Re:Linux and TPMs with systemd measured boot [video]
by Mindwipe on Monday November 06, 2023 @06:43AM
(#38161274)
Because these things are all much, much harder than just passing the decryption to the graphics card which does not permit a userland OS to see what's going on, avoiding the OS entirely. And that already happens. And has happened for years.
A TPM is useless for DRM on a general purpose computing platform because it is significantly inferior to existing widely deployed solutions.
Why don't you think that can work? Windows already limits drivers to ones signed by Microsoft - or else you have to be in "test mode" where - among other things - DRM-protected video playback is disabled!
And Windows already contains a "protected media path" component which protects encrypted DRMed video data.
Sure, there will probably be bugs in a drivers sometimes allowing for a signing bypass and then a DRM bypass if the DRM is done in software. Once they're discovered, those drivers will be blacklisted, and yes, that will mean you can't use that hardware. And the masses will blame the pirates.