UHD FAQ

[MrPenguin]

Also thanks MrPenguin for the clarification about the format. Wasn't aware it was standardized.

The KEYDB.cfg file format was created back in the early days of standard BluRays and HD-DVD, and so was designed to describe AACSv1. Any device keys, processing keys and host certificates that you will see in that file are all for AACSv1. UHD disks use AACSv2, which is an evolution of AACSv1 that allows a KEYDB.cfg file also to describe a UHD disk's DiscId, Media Key, Volume ID, Volume Unique Key and Unit Keys.

Any other notable features about a particular disk are (by convention) encoded in the entry's trailing comment:

• MKBvXX - the disk's Media Key Block version number.
• /BEE - this disk also uses bus encryption (some AACSv1 and all AACSv2 disks).
• /BD+ - this disk also uses BD+ content protection (some AACSv1 disks only).
• (BD) - a BluRay disk (presumably as opposed to a HD-DVD disk).
• (UHD) - a 4K BluRay disk.
• /UHD - an alias for (UHD) (but not widely used)

However, at the end of the day, a comment is just a comment and so it may or may not contain any of the above. Nor can you guarantee that what it says is accurate anyway.

[Coopervid]

Makemkv has fallen behind. Windows users can load keydb.cfg and decrypt with AnyDVD (UHD) or XReveal (BD and UHD). In both cases you load yor disc and start any of these programs and you need the most updated keydb.cfg. If you want to use Makemkv to create a mkv just start it after one of these programs has decrypted the disc. It's somehow stupid that Makemkv only uses VUKs since the UK is derived from the VUK and there's no logical reason for UKs to not work with Makemkv.

[MrPenguin]

(Nor is access to KEYDB.cfg currently geo-blocked. Just sayin'... )