Ralph Breaks the Internet

[SamuriHL]

I've sent a dump for this one as it's not yet supported.

[SamuriHL]

And....it's supported now. LOL

[LurkerSteve]

It should just rip using Libre without the need of keys? Mine didn't update keys and seems to be ok.

[Woodstock]

LibreDrive mode does not negate the need to decrypt the data. It will remove the revocation of a drive key from the equation, but that's only part of AACS.

[SamuriHL]

Yea, see, this is where it's not clear to me, as well. I do not claim to be ANY kind of expert on this topic at all so everything I assume that follows could be completely wrong but maybe humor me here.

The process starts with a device key afaik. The device key is checked against the MKB and a processing key is retrieved. The processing key is used to decrypt the volume unique id which gives you the volume unique key. The encrypted title keys are read from the disc and the volume unique key is used to decrypt the title key/s.

Now, again, I don't claim to have any real clue about the details, but, if you can bypass the MKB you can use a device key to get a processing key. What I believe we failed to have that prevents full AACS 2.x decryption is a valid certificate to kick off the drive's AACS decryption process allowing it to go through all those fun steps. But the certificate is what enables the drive's official firmware to read all the encrypted bits that make up the AACS decryption process (VUK, title keys, etc). If LibreDrive can read those by bypassing the AACS decryption process, wouldn't they be able to decrypt a title on the PC rather than in the drive's firmware? You'd read the data that you normally couldn't access and run the AACS decryption process on the machine. Maybe?

I'm only guessing here. Like I said, nowhere near an expert on any of this and have a very limited understanding of how it all works together.

[MagnumXL]

I've got a 4K/3D/2D/DC version from Japan (the only country that got a 3D version of this movie) and the 4K version (which I want to move the Atmos soundtrack to the 3D rip) says the key is not recognized. It didn't ask me if I wanted to submit it, but I've got the .tgz file here. Do I send it somewhere?

Edit: Nevermind. I found the address.

[MagnumXL]

I'm happy to report the Japanese 4K disc from the 4K+3D+2D set now dumps fine.

[ipkha]

Yea, see, this is where it's not clear to me, as well. I do not claim to be ANY kind of expert on this topic at all so everything I assume that follows could be completely wrong but maybe humor me here.

The process starts with a device key afaik. The device key is checked against the MKB and a processing key is retrieved. The processing key is used to decrypt the volume unique id which gives you the volume unique key. The encrypted title keys are read from the disc and the volume unique key is used to decrypt the title key/s.

Now, again, I don't claim to have any real clue about the details, but, if you can bypass the MKB you can use a device key to get a processing key. What I believe we failed to have that prevents full AACS 2.x decryption is a valid certificate to kick off the drive's AACS decryption process allowing it to go through all those fun steps. But the certificate is what enables the drive's official firmware to read all the encrypted bits that make up the AACS decryption process (VUK, title keys, etc). If LibreDrive can read those by bypassing the AACS decryption process, wouldn't they be able to decrypt a title on the PC rather than in the drive's firmware? You'd read the data that you normally couldn't access and run the AACS decryption process on the machine. Maybe?

I'm only guessing here. Like I said, nowhere near an expert on any of this and have a very limited understanding of how it all works together.

The drive itself doesn't decrypt the movie files by itself. The drive key/certificate allows the drive to get the data which is sent to the player software for decryption. Key revocation is one reason players (hardware and software) need constant updates as the content masterers try and close loopholes.

I'm sure letting the title key decryption software into the wild might make it easier for the aacs folks to foil it.

Essentially the data is double encrypted and the software to decrypt the 2nd level is being kept hidden by Mike and others to prevent updates to aacs that break it.

[SamuriHL]

That would bolster the case for automatically sending the dumps to mkv instead of having to email them. The current process works and updates usually take less than 48 hours after a dump is submitted. The key download process is already in place so we're half way there.

Sent from my Pixel XL using Tapatalk