AACS V82 Blu-ray Disc dump Help needed

[pieroraul]

Hi everbody,

I am stuck on encrypting a new blue-ray disc despite updating to the lastest version of keydb.cfg (japan).

Attached is the .tgz file.

Would be very grateful if this could be included in the next keydb.cfg update.

Thanks in advance for any help!

[tomty89]

Not so sure that MakeMKV would use keydb.cfg for regular BD (AACS 1.0), although mike might have made v82 an exception. If not you would then need to use a libaacs frontend for that (after it is added to keydb).

If you want to get it added to keydb you'd want / need to follow instruction here: viewtopic.php?t=38293

If you want MakeMKV to work for it you 'd want / need to send it to svq@makemkv.com, I think.

[Sayaka]

Not so sure that MakeMKV would use keydb.cfg for regular BD (AACS 1.0), although mike might have made v82 an exception.

Before I had LibreDrive enabled, I had to use FindVUK to find the correct VUKs for at least two "v82" discs, and I'm pretty sure MakeMKV was able to decrypt those discs only after reading the entries from the updated KEYDB.cfg file.

[tomty89]

I see. I don't have any v82 discs, but last time I tested with a regular BD encrypted backup (a v7x one IIRC) without discatt.dat (presumably where the volume ID is stored), MakeMKV simply stalled when I try to open it (even when keydb has VUK for the disc), while it works fine with a UHD BD encrypted backup (also without discatt.dat).

Because it wouldn't make much sense for it to just work differently for v82 discs (since AFAICT once the host cert/key is revoked by the v82 MKB, it will no longer be able to retrieve volume ID from even older discs without LibreDrive), so I wasn't sure keydb would be used for regular BD at all. (Perhaps it's because for regular BD the keydb/hk routes would only be taken when the volume ID retrieval fails due to host cert/key revocation, so the routes would kick in only when it's accessing an actual disc, whereas for UHD BD volume ID retrieval wouldn't even be attempted anyway, so it works even with a backup.)

P.S. btw does it mean that MakeMKV has a host cert/key that is not revoked until v82? because the host/key cert in keydb is revoked in v76 or so (as per the comment), which is sort of why I'm quite confused what makes v82 "special" to MakeMKV. (Also, does it also mean that "Added support for AACS v82" in 1.18.0 is essentially only "partial support", i.e. just a "device key" that works with the v82 MKB (or corresponding "processing key")? In other words, the "support" covers only LibreDrive? Or is the story even more complicated?)

[pieroraul]

Thank you for your reply. I realized the attachment in my post didn’t upload successfully. I’ve already sent the dump file to the team’s email address. Thanks again for your tip.