Re:Update on HTML5 Video for Netflix
by Rusky on Wednesday March 22, 2017 @08:53PM
(#13936574)
What's to stop someone reverse engineering the blob before it's loaded into an SGX enclave? I don't understand it very well so I could be missing something, but wouldn't that at least let someone document how the DRM works even if not running their own implementation?
[ Parent
| on HN ]
Re:Update on HTML5 Video for Netflix
by bubblethink on Wednesday March 22, 2017 @11:54PM
(#13937279)
It would be of no use (and the code can also be encrypted for additional obfuscation). There is no private data in the blob. The blob communicates to mothership once it's safe inside the enclave, and that's when sensitive data is transmitted over an encrypted channel which only the blob can decrypt inside the enclave.
We still have the good old DMCA to make sure that anyone who does do that kind of thing could be punished to a ridiculous extent.
Re:Update on HTML5 Video for Netflix
by ndesaulniers on Wednesday March 22, 2017 @09:42PM
(#13936799)
Digital signatures. Not that I actually know how it's implemented, but I would expect someone like Netflix to pay Intel for the build infrastructure to be able to build signed blobs that the SGX will load.
The "someone" in your hypothetical can modify the blob, but then they won't be able to resign the blob, so SGX will fail to load it.