AFK88L wrote: Sat Jan 17, 2026 1:20 pm
The below release appears to be missing from the public keydb. I would like to contribute, however for this disc I found it was already natively supported by MakeMKV so the program wouldn't create a disc dump.
I tried following the instructions in
this post to force MakeMKV to create the dump, but it would not work for me.
Hey AFK88L, the instructions that I wrote in that post were intended for AACS 2.0 discs rather than AACS 1.0. To be honest, I'm actually surprised that MakeMKV v1.18.2 generated a disc dump for an AACS 1.0 MKBv68 disc. MakeMKV v1.18.2 has native support for AACS 1.0 MKBv1-MKBv81 without the need for external/downloaded title specific keys. So it really should've used one of the AACS 1.0 device/processing keys bundled with MakeMKV instead of generating that disc dump.
AFK88L wrote: Sat Jan 17, 2026 1:20 pm
I eventually got a disc dump generated by MakeMKV (below) but only when also running in a VM (Win10 for the VM, vs. Win11 on my main host... not sure if that has a bearing).
I believe the VM aspect is not relevant here.
AFK88L wrote: Sat Jan 17, 2026 1:20 pm
In light of this, for discs MakeMKV already natively supports but are missing from the public keydb, what is the process? Is there any consistent way to force MakeMKV to create a disc dump so we can submit the required files?
The main components of a disc dump file are:
1.
discatt.dat - Contains the volume ID
2.
MKB_RO.inf - Contains the encrypted media key (MK) for your disc and the media key verification data used to validate the media key
3.
Unit_Key_RO.inf - Contains the encrypted unit key(s)
4.
kv.dat - Contains several encrypted aligned units (6,144 bytes each) from one or more M2TS files. It is important that these are read after bus encryption has been disabled.
Technically all of the title-specific keys can be derived with only the first three files. The kv.dat file is used to validate the resultant unit keys. This also has the effect of validating the volume ID (VID) and the volume unique key (VUK). Any small M2TS file from the disc can be used as a substitute for the kv.dat file as long as bus encryption has been disabled before copying the file.
AFK88L wrote: Sat Jan 17, 2026 1:20 pm
Alternatively, is there another way to
manually create a disc dump without MakeMKV? What files are actually required in the tgz to have it added to the public keydb?
Rough outline:
1. Use MakeMKV to start creating an
encrypted folder backup of a disc
2. Stop the backup once the discatt.dat/discattd.dat file has been created and at least one M2TS file has been copied
3. Make a new folder for your synthetic disc dump
4. Copy the discatt.dat file and the smallest M2TS file out of the (incomplete)
encrypted backup folder into your synthetic disc dump folder
5. Copy the entire AACS directory from your disc into your synthetic disc dump folder
6. Zip up the synthetic disc dump folder, upload it to a file host and post a link here
The process isn't too streamlined but there will be improvements made throughout this year as some new tools and drive firmware options become available.
FindVUK on Windows can also be used to generate MKBv1-MKBv81 AACS 1.0 disc keys without MakeMKV or any other commercial tool as long as your drive hasn't been exposed to AACS MKBv82