EME, CDM, AES, CENC, and Keys – Building Blocks of DRM

Re:EME, CDM, AES, CENC, and Keys – Building Blocks of DRM by grishka on Tuesday November 03, 2020 @09:55AM (#24980124)

Thanks for linking this talk, it was indeed interesting. Especially the part where he said that "if the hack costs more than 10 games, we're fine". Indeed, you probably aren't breaking this thing unless you have millions of dollars worth of equipment and the expertise to use it.

But then video game consoles are special. They were always these closed, tightly-controlled ecosystems. General-purpose devices, like phones and computers, typically lack this kind of integration between their components. Yes, there's ARM TrustZone, and that's about it. Thankfully. And I'm not aware of anything similar on x86 PCs (besides the Apple T2, which was recently compromised).

[ Parent | on HN ]

Re:EME, CDM, AES, CENC, and Keys – Building Blocks of DRM by Mindwipe on Tuesday November 03, 2020 @12:35PM (#24981831)

Most GPUs now have hardware backed support for DRM. That's why those GPUs get 4K Netflix.

The compromise of Apple's T2 chip was significantly overstated.

[ Parent | on HN ]

Re:EME, CDM, AES, CENC, and Keys – Building Blocks of DRM by vengefulduck on Tuesday November 03, 2020 @11:28AM (#24981088)

Intel SGX?

[ Parent | on HN ]

Re:EME, CDM, AES, CENC, and Keys – Building Blocks of DRM by grishka on Tuesday November 03, 2020 @01:10PM (#24982237)

I've seen this name but still don't understand where's its root of trust. In other words:

- How does the program making use of it make sure it's not been patched so the code that's supposed to run in the enclave runs without one?

- How does it know it's not being run on an emulated CPU or in a VM? And that those checks haven't been patched out, too?

- How does it make sure the OS is cooperating? I assume there is some cooperation required from the kernel at least.

[ Parent | on HN ]