Browsing hashed keys?

[MrPenguin]

Hi,

I am assuming that MakeMKV's "hashed keys" database is here:

Code: Select all

$ tar tvf ~/.MakeMKV/_private_data.tar 
-rw-r--r-- 0/0              68 1970-01-01 01:00 hkd_0000005a.bin
-rw-r--r-- 0/0              28 1970-01-01 01:00 hkd_0000005b.bin
-rw-r--r-- 0/0             188 1970-01-01 01:00 hkd_0000005c.bin
...
-rw-r--r-- 0/0             916 1970-01-01 01:00 hkd_00000241.bin
-rw-r--r-- 0/0             756 1970-01-01 01:00 hkd_00000242.bin
-rw-r--r-- 0/0            7456 1970-01-01 01:00 --index-2941D54045E3B11CB9A59E919B14786D5237ADFC.bin
-rw-r--r-- 0/0             512 1970-01-01 01:00 --index-F8F0FB56931D8E1656F061A3ED313D9CE5F257ED.bin

Is there any way of browsing this data please? Come to think of it, does anyone even know how this data was compiled in the first place?

Thanks for any insights here.

Edit: Has this been compiled from everyone's emails to svq@makemkv.com?

[SamuriHL]

The data is encrypted and there is no way to read it. It's not meant for our consumption like a keydb.cfg file. It's meant for MakeMKV to use internally. The dumps you email in are used to generate the unit keys and/or Volume Unique Keys (VUKs) used to decrypt individual discs. That is what is stored in the hashed key binary data.

[MrPenguin]

The data is encrypted and there is no way to read it. It's not meant for our consumption like a keydb.cfg file.

That's a pity, because I learnt a lot about AACS 1.0 by examining keydb.cfg .