Reading AACS dump file to integrate into keydb.cfg

[bdripguy]

Hi. I bought a BD that contains AACS2.0/C v82 for the purpose of trying out if I can bypass the copy protection. That is my only UHD BD and to my surprise it came out with a "revoked certificate" error. I tried this with VLC with 1.03MK firmware for BU40N.

The jewel case came with two BDs, actually. One which is HD and another one which is UHD. The HD one gives me the AACS error. The UHD one only shows a crappy 144p thumbnail. Both seem to use the same header or something. Maybe Marvel messed up the labels of which disk is which?

All the other BD's I currently have (300, Rocky Balboa, Iron Man, Indiana Jones kingdom of cracked skull, etc) seem to play just fine. I guess that's because they use AACS and not AACS2.0. I am able to copy all the contents just fine (or at least that's what gnome-disks says).

I used MakeMKV trial as a sanity check. I would prefer if I could just find the key in the dump and neatly stow it away in my keydb for future use.

So, can I do that or? I just want to read the BD. No muxing or reencoding or whatever

[MartyMcNuts]

Hi. I bought a BD that contains AACS2.0/C v82 for the purpose of trying out if I can bypass the copy protection. That is my only UHD BD and to my surprise it came out with a "revoked certificate" error. I tried this with VLC with 1.03MK firmware for BU40N.

The jewel case came with two BDs, actually. One which is HD and another one which is UHD. The HD one gives me the AACS error. The UHD one only shows a crappy 144p thumbnail. Both seem to use the same header or something. Maybe Marvel messed up the labels of which disk is which?

All the other BD's I currently have (300, Rocky Balboa, Iron Man, Indiana Jones kingdom of cracked skull, etc) seem to play just fine. I guess that's because they use AACS and not AACS2.0. I am able to copy all the contents just fine (or at least that's what gnome-disks says).

I used MakeMKV trial as a sanity check. I would prefer if I could just find the key in the dump and neatly stow it away in my keydb for future use.

So, can I do that or? I just want to read the BD. No muxing or reencoding or whatever

No you won't find the key in the dump.

MakeMKV doesn't natively decrypt AACS v82 and should generate a dump file. This dump file should be emailed to svq@makemkv.com for processing and a hashes key will then be added to the HK database.

Additionally, you can create a post in the Public KeyDB Submissions thread, providing all of the required details/files and a record can be added to the Public KeyDB.

[keydb_helper]

I tried this with VLC with 1.03MK firmware for BU40N.
...
I would prefer if I could just find the key in the dump and neatly stow it away in my keydb for future use.

There are essentially three cases for disc dumps produced by the BU40N or any other UHD-compatible LG/LG-rebranded drive.

Case 1 - AACS 1.0:
The volume ID (VID) is unobfuscated within the discatt.dat file. You can use this with the publicly available AACS 1.0 device keys to derive all of the required disc keys for any disc from MKBv1 to MKBv82

AACS 2.0:
The volume ID (VID) will still be unobfuscated within the discatt.dat file. You will need to iterate through the known UHD media keys in the keydb.cfg file. If you use each candidate media key to decrypt the media key verification data (record 0x86 within any AACS 2.0 MKB_RO.inf file) and compare the first 8 bytes of the result to the expected hex output of "0123456789abcdef" you can identify the correct media key.
Case 2 - If you find a known media key which produces the expected output, you can use it with the unobfuscated VID to derive all of the other keys for your disc.
Case 3 - If there is no matching media key, you'll need to post your disc dump to the public keydb submission thread so that the disc keys can be derived.

These three cases are also relevant for most Pioneer disc drives. The exceptions are the BDR-UD04 and a few other drives which return obfuscated VID values. These disc dump files will need to be posted to the keydb submission thread even when the media key is known to the keydb.