zlacker

It's signed?

Sure you can fake the results of an attestation in your fork, but your fork would be using your own key to sign the response, a key that the site can reject.

>>jabban+(OP)
Ah, we’ll also have to extract the key from chrome. It’s no worse than WideVine.

>>freeon+Jq
Has that been extracted already? I have to admit I'm behind on the current state of browser DRM...

Also I wonder if in the future this would require attestation of the entire chain: secure UEFI validated by key burned in CPU, validates secure boot os that prevents "hacking tools", which validates secure Chrome, which attests secure websites...

Truly royally screwed at that point...

>>freeon+Jq
There is no key in chrome, the signing is done via a 3rd party server.

>>jabban+2u
The current state of DRM is that you have to find a hardware vulnerability in order to extract a certificate. With this you can now decrypt DRM content, but you have to be careful not to get that key blacklisted.

>>freeon+Jq
I don't believe any of the HD widevine keys have been revealed.

I would practically guess the keys that did get revealed were deliberately leaked, low stake keys, that keep people still willing use to use widevine platforms at low res without being angry.

>>freeon+Jq
No, you'll need to extract the TPM secureboot keys from Microsoft headquarters. Good luck with that