UHD FAQ

[keydb_helper]

I have the KeyDB_Helper ver 1.0.2.1
Where do I download the newest version from? Link seems to be broken...

I think 1.0.2.1 is the newest version and the Mediafire link is still accessible:

KeyDB Helper (Windows Only)

https://www.mediafire.com/file/i0zkya2c ... .1.7z/file

...
============
1.0.0.1 Added notification if title supported by MakeMKV
...
1.0.2.1 Added better formatting for output text; Fixed bug where findvuk would hang during validate if new drive was found; Fixed bug where keydb.cfg was locked by rogue running findvuk process

[SamuriHL]

Yup 1.0.21 is the latest. The MF link should still be working fine. I haven't changed anything.

[jatenk]

Apologies if this has been answered before or it's supposed to be obvious, but how does the process of generating a key from a dump file actually work? If all that's needed to create a key from a dump file was included on the disc on hand, it would be possible to do this on the same machine, which it clearly isn't. I'd like to know where the file actually goes and what the key generation looks like from a practical and, possibly, mathematical perspective.

[MrPenguin]

Apologies if this has been answered before or it's supposed to be obvious, but how does the process of generating a key from a dump file actually work?

You can start with basic AACS information, which includes the specifications, and which should tell you about AACS 1.0. AACS 2.0 is "like" AACS 1.0, but with some upgrades.

There are obviously some missing pieces in all of these, i.e. a set of secret keys which makes the algorithms work. There are also some publicly available keys for AACS 1.0, which AACS-LA actively revokes whenever it can. But there is nothing publicly available for AACS 2.0, and this is almost certainly because such things are much harder to come by than for AACS 1.0.

[BrianInSC]

KeyDB Helper (Windows Only)

https://www.mediafire.com/file/i0zkya2c ... .1.7z/file

* Extract it to a folder
* Run it...it will download a copy of FindVUK and configure it

The following functions are available:

* Synchronize - Syncs the keydb.cfg file using FindVUK and then copies it to the MakeMKV data directory
* Validate - Validates your disc in the KeyDB file. This is a VERY good thing to be doing with all your discs!! It helps to maintain the integrity of the KeyDB.
* Disc Info - Shows you the information for your disc including the disc ID. If your KeyDB.cfg file contains device keys and/or processing keys, it COULD, in theory, maybe use those to ADD entries to the KeyDB. You know, for those pesky MKB v82 blu-rays everyone is loving.
* Disc Hash - Content Hash validation for the disc. I personally use this on my mounted protected ISOs after creating them to validate they're good but you can use it directly on a disc if you want, it'll just be slower
* Search - Allows you to search for a disc ID to see if it's in the keydb
* Settings - Allows you to specify additional directories to copy the keydb.cfg file to

The MKB v82 device key has been added to the public keydb.cfg. You no longer need to add it using the Fix functionality in my tool.

Once in a great while when the luck of the stars work in your favor, SOMETIMES on rare occasions this disc info process might help you find a VUK for a UHD that you're waiting for. To be clear, this code contains ZERO keys and there are NO public AACS 2.x processing keys...but sometimes you get lucky with other entries that could be in the KeyDB just waiting to be taken advantage of at times.

NOTE: This will not work on certain Pioneer drives. The VID needs to be able to be read correctly for it to work.

If you see [MakeMKV SUPPORTED]: FALSE it means that the KeyDB entry does not contain a VUK. You should post a dump or a link to a dump for your disc to see if someone can add a full entry to the KeyDB for your disc

That's all it does. But should make things easier for those who use the KeyDB in concert with MakeMKV.

NOTE: I added an experimental feature to check discs that have an AACS directory but the contents of the disc are NOT encrypted. I don't have any such discs myself so I couldn't test it but in theory it might tell you when it detects that. It also might present false positives so let me know how you make out with this one.


NOTE: This will require .NET 8 Framework runtime be installed. You can find the latest here:

https://dotnet.microsoft.com/en-us/download/dotnet/8.0

Get the Windows X64 installer.

============
1.0.0.1 Added notification if title supported by MakeMKV
1.0.0.2 Fixed path not found exception when attempting to create an empty keydb.cfg file on startup
1.0.1.0 Enhanced Disc Info functionality; FindVUK Validate disc functionality added
1.0.1.1 Log inflation bug...accidentally left debug logging statement in causing log to grow exponentially...oops
1.0.1.2 Add unit key validation and keydb entry updating when local validation succeeds but differs from keydb
1.0.1.3 Forgot to compare the actual unit keys
1.0.1.4 Lots of internal bug fixing
1.0.1.5 Added new Fix... option for updating the keydb.cfg in certain circumstances
1.0.1.6 Add tooltips; Add Disc Hash; Faster VID parsing; Fixed bug in Fix function if header is missing
1.0.2.0 Removed fix functionality as it was no longer needed; Added settings button to configure additional directories to copy the keydb.cfg to; Added experimental detection of discs with AACS directory that aren't actually encrypted (let me know how that works for you)
1.0.2.1 Added better formatting for output text; Fixed bug where findvuk would hang during validate if new drive was found; Fixed bug where keydb.cfg was locked by rogue running findvuk process

Can I send you a kofi or something? This neat little app did me good!

[SamuriHL]

Totally not necessary. I'm glad you find it useful. I wanted to make using Nalor's FindVUK program easier for people who aren't used to dealing with command line that's all.

[PeteG]

Thanks a lot for this app. My first UHD rip on a new drive, flashed as per this forum, totally failed. After reading around a bit, got your KeyDB Helper, ran it, the keyDB file was installed to MakeMKV and tried rip again with smooth success. Thankyou.

[DpreDpvtas]

I want to know if the newly released OmniDrive firmware for blu-ray drives is compatible to use with MakeMKV? I want to flash my drive with that firmware just to dump game discs, as well to be able to dump 4k blu-ray movies.

[SamuriHL]

I rebranded KeyDB Helper to KeyDB Assistant to avoid any confusion with the user keydb_helper. No functionality changes.

[ThatDudeRandy]

Where is the current link to find KeyDB Assistant...the media fire link is broken

[nicholfd]

Where is the current link to find KeyDB Assistant...the media fire link is broken

The Media Fire link in the main post just worked for me: viewtopic.php?f=12&t=16883&p=166510&hil ... nt#p166510

Thanks,
Frank

[nekno]

NOTE: I added an experimental feature to check discs that have an AACS directory but the contents of the disc are NOT encrypted. I don't have any such discs myself so I couldn't test it but in theory it might tell you when it detects that. It also might present false positives so let me know how you make out with this one.

I don't know if you're still looking for reports, but the Disc Info feature worked great with the unencrypted Stranger Things S2D2 disc as of KeyDB Assistant 1.1.0.0.

Code: Select all

=======================================================
  DISC INFORMATION
=======================================================
-------------------------------------------------------
NOTICE: Disc Structure Without Encryption
This disc has an AACS directory but content is NOT encrypted.
This is common for some UHD discs.
No decryption keys are needed for this disc.
-------------------------------------------------------

This being my first run-in with an unencrypted disc, it took me a while to figure out the implications and find the instructions on the forum here, for how to work around it with MakeMKV.

Feature request: Would it be possible to work this block of info into the Validation step as well?

The validation just ends with a series of errors about the key upload, and doesn't indicate what's going on (see below). If it's coming from FindVUK, perhaps there's a return code you can detect that would trigger you to run your Disc Info code? Or is this all properly the responsibility of FindVUK?

Code: Select all

-------------------------------------------------------
14:16:23 - --- Write entry in backup-keydb file ---
-------------------------------------------------------
 
{snip}
 
14:16:23 - Identical entry already present in keydb-file - file is not changed
 
14:16:23 - ERROR! Couldn't create BlurayMetaXML!
14:16:23 - ERROR! Couldn't upload entry to OnlineDB
14:16:23 - ERROR! Validate_UploadResultToOnlineDatabase failed!
14:16:23 - ERROR! ShowResult for mode ValidateDisc failed!

[SamuriHL]

Yea that’s all findvuk under the covers. Disc info is mine. They really don’t interact at all.

[MartyMcNuts]

Yea that’s all findvuk under the covers. Disc info is mine. They really don’t interact at all.

So, in your Disc Info comment, can you add the steps so people know what to do?

1. Backup to folder (leave decrypt unchecked)
2. Delete the AACS directory
3. Open index.bdmv in MakeMKV
4. Create MKV file.

[nekno]

Yea that’s all findvuk under the covers. Disc info is mine. They really don’t interact at all.

Copy that. So handling the return code from FindVUK could still work, but I get it if you don't want to add it for this edge case.

1. Backup to folder

Backup to folder (with decrypt unchecked). That's important, or you'll be buggered right back in the same spot failing to decrypt the disc.

Explaining the workaround would save / would have saved us poor souls countless hours, but I would understand if he's reluctant to add output about another specific app (MakeMKV).

Since it's a known issue, do we know why this hasn't been prioritized to get fixed in MakeMKV (other than 'all features are unimplemented by default')?