Dr. House - Decryption failed

[obst_terminator]

Hello everyone,

First of all, English is not my native language. If I express myself awkwardly, feel free to ask for clarification, and I will try to rephrase my sentences accordingly.
I’m new here, and with the help of this really great software, I’ve already managed to digitize part of my BluRay collection.
Currently, I’m stuck a bit because I can’t decrypt a few discs from the series "Dr. House." So, I’m asking for help.

My setup: I rip the BluRay discs using a Playstation 3 to .ISO files. Then I copy them to my PC.

I’m using the latest MakeMKV client (Version 1.17.9) licensed on Arch-Linux.

In case of a decryption error, .tgz files are saved in my home/.MakeMKV/ folder. I’ve attached them here:

MKB_v49_House_-_Season_1_Disc_4_6CB2.tgz

(148.6 KiB) Downloaded 45 times

MKB_v49_House_-_Season_1_Disc_3_5346.tgz

(147.39 KiB) Downloaded 43 times

MKB_v47_House_-_Season_1_Disc_2_AD48.tgz

(146.19 KiB) Downloaded 41 times

Thank You all!

[MrPenguin]

My setup: I rip the BluRay discs using a Playstation 3 to .ISO files. Then I copy them to my PC.

I doubt this will work because MakeMKV needs to access the BluRay disk and drive directly. Your ISO will be missing the Volume ID (VID) metadata, which is part of the BluRay's "lead-in" section. Without the VID, no-one can calculate a disk's Volume Unique Key (VUK). And MakeMKV wants to know the disk's VUK.

Have you tried downloading the latest KEYDB.cfg file, copying it into MakeMKV's data directory (i.e. where MakeMKV also writes its TGZ dump files) and restarting MakeMKV? This might help, if the KEYDB.cfg happens to contain complete entries for your disks. Failing that, you're going to need to put those disks into another BluRay drive that is attached to your PC, or possibly even boot your PS3 into Linux and run MakeMKV there instead.

If you just want to play those disks using VLC then KEYDB.cfg would only need to contain their Unit Keys, rather than their VUKs.

[obst_terminator]

Hello Mr. Penguin,
thank you for your reply. I have understood the explanation. I'm just a bit confused that it worked with disk 1, but not with the other 3 disks. I have already created several rips in this way and then processed them with MakeMKV.
I will create a new rip as a test. To be honest, at the moment I simply don't have the money to buy a BluRay drive.

I just downloaded the latest KEYDB.CFG this morning and put it in the appropriate folder.

If the .ISO is missing elements that I can only get with a drive, then I'll probably have to skip it for now.

But thanks for the input!

[MrPenguin]

thank you for your reply. I have understood the explanation. I'm just a bit confused that it worked with disk 1, but not with the other 3 disks.

The only explanation is that MakeMKV must have already known the keys for your disk 1, making calculation unnecessary (although equally impossible). However, MakeMKV clearly didn't know the keys for disks 2, 3 and 4.

I have already created several rips in this way and then processed them with MakeMKV.

Sure, this method is fine for BDs without bus encryption, so long as MakeMKV already knows the decryption keys.

Seeing as you are a Linux user, you can calculate a disk's ID for KEYDB as follows:

Code: Select all

$ sha1sum AACS/Unit_Key_RO.inf

You can then determine whether any of your disks already have entries in KEYDB.cfg.