I’m in no way a Google fan boy (rather the opposite), but IMHO this is backwards.
We have a (at some levels) shits DRM because of Google providing a semi-secute DRM stack.
If you want to go full DRM, there is no way around a key store, so for most (user) linux installations unachievable.
Without widevine nobody would give a fuck about Linux DRM anyway and Netflix, Amazon and friends would be out of reach for “normal” Linux users.
That said: fuck DRM, fucking cancer.
Not just key store, since you can quite easily use a secure enclave on Linux just as on any other platform.
The key issue is the render stack. On Windows and MacOS, providers can get certain assurances that the parts of the stack that take their decoded DRM’ed content and draw it into a window, get composited with other windows, have various transforms applied, and actually get things out to an HDCP-supporting monitor are all unmodified and (at least to a certain extent) immune to screen captures and other methods of getting the plain un-encrypted media stream. Linux on the desktop almost never provides those assurances. The only ones that really do are ChromeOS and Android–and both of those provide relatively high trust DRM as a result.
DRM doesn’t work in practice to prevent piracy, but if you drink that cool-aid and assume for a moment that DRM actually worked, then Linux is basically impossible to provide verified DRM content to with the current landscape in the way that Windows, MacOS, CrOS and Android/iOS do
Absolutely! You don’t get the former (keys) because you can’t get the later (secure render stack) as a “normal” Linux user.
That said, one thing you got technically(!!) wrong:
You can get a secured (stack) and certified (keys) Linux, if you close it up properly… Source: I worked a little bit on one of those, and yes, I’m ashamed, and yes, I’m expecting a bit of hell time for it… Was a fun task though.
