Public KeyDB Disc Submissions

[caseablee]

Disc type: UHD
Disc dump filename: MKB20_v77_Fast_and_Furious_6_3A77
Drive: BDR-XD07U
Drive firmware: 1.03
LibreDrive status: Enabled
Did you sync the public keydb within the last 15 minutes? Yes
Have you verified that all submission links are accessible in incognito/private browsing? Yes
MKB_RO.inf link (Do not just extract the MKB_RO.inf file from the disc dump file - copy it from the disc): https://drive.google.com/drive/u/0/fold ... 8fGY-7r5j_
Disc dump link: https://drive.google.com/drive/u/0/fold ... 8fGY-7r5j_

[tomty89]

Hello. So I have an old title (regular / non-UHD BD) with MKBv37 and this drive that hasn't been inserted with disc with a newer MKB. With the host cert/key provided in KeyDB I've managed to obtain the VUK through libaacs, and I would like to have it added to the KeyDB (if key for such older title are still being accepted).

And the question is, what should I do? Should I just post the VUK et al. here? Or do I have to run FindVUK anyway? (I'm on Linux but probably it works through wine?)

P.S. AFAIK both the drive and the disc is non-BEE, if that matters. I mounted the filesystem and used rsync -rvc to compare its content with an encrypted backup made with MakeMKV, and as per the result they are identical. However I haven't exactly "validated" the VUK by decrypting it with libaacs (and compare the result with the decrypted backup from MakeMKV).

[OldCavalier]

Deathstalker 1983

https://drive.google.com/drive/folders/ ... 1iJW1Oplp5

[OldCavalier]

DeathStalker II Arrow Video US

https://drive.google.com/drive/folders/ ... fM_unQXwqt

[OldCavalier]

Deathstalker 2025 Arrow Video US Version

https://drive.google.com/drive/folders/ ... yrvdPoJ9rm

[badboy]

Disc type:UHD
Disc ID:B3BCCC71180573C3E75634A78043466957B043A1
Disc dump filename:MKB20_v82_LA_COLLINE_A_DES_YEUX_-_4K_UHD_7CC6
Drive:BW-16D1H-U
Drive firmware:A204
LibreDrive status:Enabled
Did you sync the public keydb within the last 15 minutes? YES
Have you verified that all submission links are accessible in incognito/private browsing? YES
MKB_RO.inf link :https://drive.google.com/file/d/1fVsk44 ... VMi9CgaawT
Disc dump link:https://drive.google.com/file/d/1Zqx7U7 ... V3ish7Ema8

[MrPenguin]

And the question is, what should I do? Should I just post the VUK et al. here? Or do I have to run FindVUK anyway? (I'm on Linux but probably it works through wine?)

P.S. AFAIK both the drive and the disc is non-BEE, if that matters. I mounted the filesystem and used rsync -rvc to compare its content with an encrypted backup made with MakeMKV, and as per the result they are identical. However I haven't exactly "validated" the VUK by decrypting it with libaacs (and compare the result with the decrypted backup from MakeMKV).

FindVUK works fine inside a wineconsole on Linux. You would need to add an entry for your disk to your KEYDB.cfg file, and then execute "findvuk validateDisc" to have FindVUK prove that your entry is correct, and then upload it into the database. For example:

Code: Select all

$ wineconsole findvuk validateDisc drive=e

where your UHD drive would be identified by letter E.

You calculate the disk's ID like this:

Code: Select all

$ sha1sum /path/to/your/disk/AACS/Unit_Key_RO.inf

If your disk did use BEE then either libaacs would need to know the correct RDK to use, or you'd need to use MakeMKV to disable bus encryption before invoking FindVUK. Note also that FindVUK.ini has a "Disable_Bus_Encryption_Cmd" option:

If you know the RDK then you don't need to disable bus encryption:

Code: Select all

Disable_Bus_Encryption_Cmd =

Or if you need a "dummy" command for FindVUK to execute so that it knows you have already disabled BE yourself:

Code: Select all

Disable_Bus_Encryption_Cmd = hostname.exe

Remember that FindVUK's libaacs will have a totally different KEYDB.cfg file to $HOME/.config/aacs/KEYDB.cfg, and cache to $HOME/.cache/aacs

[keydb_helper]

Thanks to everyone who followed the template and provided new disc dump files. The following UHD discs have been added to the public keydb (new media keys are indicated with an asterisk):

Code: Select all

*MKB20_v77_Fast_and_Furious_6_3A77
*MKB20_v82_Beast_-_Legenden_entstehen_im_Käfig_E938
*MKB20_v82_Deathstalker_(1983)_64E4
*MKB20_v82_Deathstalker_(2025)_10DA
*MKB20_v82_Deathstalker_II_9182
*MKB20_v82_LA_COLLINE_A_DES_YEUX_-_4K_UHD_7CC6
*MKB20_v82_Rumble_in_the_Bronx_UHD (Hong Kong version - 0x3C105928B879DE0620420A73B91F2690D7DA3D29)
*MKB20_v82_The_Descent_AE32
*MKB20_v82_THE_DRAMA_771A
*MKB20_v82_THE_ELEPHANT_MAN_F918
*MKB20_v82_The_Money_Pit_3862

[Thragg_was_taken]

am having trouble ripping my copy of terrifer 3

[Woodstock]

am having trouble ripping my copy of terrifer 3

Giving people some information about errors received would be normal, when sending a message in this thread. The first message in the topic describes what is needed.

[Thragg_was_taken]

apologies thats a fair point

MakeMKV v1.18.4 win(x64-release) started
Using LibreDrive mode (v06.3 id=866A98CB9C4E)
Using direct disc access mode
Loaded content hash table, will verify integrity of M2TS files.
The AACS dump file "C:\Users\jhysl/.MakeMKV/MKB20_v77_Terrifier3_53A7.tgz" was successfully sent for analysis
The volume key is unknown for this disc - video can't be decrypted
Failed to open disc

Disc type: UHD
Disc ID: b2b8a698713d002393e2a649b5059b58f562b01e
Disc dump filename: MKB20_v77_Terrifier3_53A7.tgz
Drive: HL-DT-ST BD-RE BU40N (Verbatim External Slimline 4K)
Drive firmware: 1.03 MK (Patched)
LibreDrive status: Enabled
Did you sync the public keydb within the last 15 minutes? No
Have you verified that all submission links are accessible in incognito/private browsing? Yes
MKB_RO.inf link (Do not just extract from the dump - copy from the disc):[/bMKB20_v77_Terrifier3_53A7.tgz]
Disc dump link:https://mega.nz/file/uGQ0ULDb#Uf91XnnL9 ... Du7Li_9gx8
https://mega.nz/file/vbhglAib#1J1pVZbpZ ... hsTy9EKqUg

[tomty89]

FindVUK works fine inside a wineconsole on Linux. You would need to add an entry for your disk to your KEYDB.cfg file, and then execute "findvuk validateDisc" to have FindVUK prove that your entry is correct, and then upload it into the database. For example:

Code: Select all

$ wineconsole findvuk validateDisc drive=e

where your UHD drive would be identified by letter E.

Actually in my case I simply need to go for the AACSkeys method, since it's a regular BD and the host cert/key in KeyDB hasn't been revoked in drive yet.

Btw I almost gave up because things didn't work at the beginning. The different methods either gave me weird "BRAKEYS_DriveNotFound" error or "AACS folder on disc is not accessible". Only after messing with aacs_info from libaacs (which gives me many "corrupt" lines when I pass the device node as argument, while bd_info from libbluray works just fine) and then I realize not all programs / libraries can deal with the UDF filesystem "directly" like libbluray, and therefore for FindVUK to work through wine, I need to have the filesystem on the disc mounted (even though the "drive letter / dosdevice" is / has to be a symlink to the device node, namely /dev/srN...)

(Although most people that is not like me but uses a DE / prefers "automounting" wouldn't even bump into this problem in the first place I guess...)

[mwwtdl]

Disc type: UHD
Disc ID: 0xA4A210D6257EB714200175EBBF520D7931CD4D1C
Disc dump filename: MKB20_v82_THE_WARNING_6E7A.tgz
Drive: HL-DT-ST BD-RE BU40N
Drive firmware: 1.03 (LibreDrive patched)
LibreDrive status: Enabled
Did you sync the public keydb within the last 15 minutes? Yes
Have you verified that all submission links are accessible in incognito/private browsing? (verify this before posting — open an incognito window and confirm the Google Drive link works)
MKB_RO.inf link: N/A (dump file is 3.29MB, full dump)
Disc dump link: https://drive.google.com/file/d/1Yh4kTa ... sp=sharing

[hover]

hi, please help me with these two, thanks.

Drive: HL-DT-ST BD-RE BU50N
Drive firmware: 1.0
LibreDrive status: Enabled
Did you sync the public keydb within the last 15 minutes? Yes
Have you verified that all submission links are accessible in incognito/private browsing? Yes

Disc type: UHD
Disc ID: 0x0A110200738B0CB573F232363B525971380170FC
Disc dump filename: MKB20_v76_Spider-Man-_Across_The_Spider-Verse_0D04
MKB_RO.inf link: https://drive.google.com/file/d/17Nl0IM ... drive_link
Disc dump link: https://drive.google.com/file/d/12-64d3 ... drive_link

Disc type: UHD
Disc ID: 0xE8D39774C5708088ADE30E8FED36A3765733CC6E
Disc dump filename: MKB20_v68_SPIDER-MAN_INTO_SPIDER-VERSE_3BF1
MKB_RO.inf link: https://drive.google.com/file/d/1yK1Fum ... drive_link
Disc dump link: https://drive.google.com/file/d/1niFSOf ... drive_link

[keydb_helper]

Thanks to everyone who followed the template and provided new disc dump files. The following UHD discs have been added to the public keydb (new media keys are indicated with an asterisk):

Code: Select all

*MKB20_v68_SPIDER-MAN_INTO_SPIDER-VERSE_3BF1
*MKB20_v76_Spider-Man-_Across_The_Spider-Verse_0D04
*MKB20_v77_Terrifier3_53A7
*MKB20_v82_The_Super_Mario_Galaxy_Movie_8CD8

am having trouble ripping my copy of terrifer 3

apologies thats a fair point

Nice save.

Disc type: UHD
Disc ID: 0xA4A210D6257EB714200175EBBF520D7931CD4D1C
Disc dump filename: MKB20_v82_THE_WARNING_6E7A.tgz

Hey mwwtdl, your disc was added to the keydb on June 2. This was fortunate as your disc dump is incomplete due to your drive encountering a transient fault. Whenever you see output like this in your log it means the disc dump file is not going to be usable by either the MakeMKV team or the keydb community:

Code: Select all

002004:0000 Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - KEY NOT PRESENT' occurred while issuing SCSI command A40..002000800 to device 'SPTI:\Device\CdRom0'
DEBUG: Code 0 at (FS[Bh5JS4pc>jdxo:213130306
002004:0000 Error 'Scsi error - ILLEGAL REQUEST:COPY PROTECTION KEY EXCHANGE FAILURE - KEY NOT ESTABLISHED' occurred while issuing SCSI command AD010..080002400 to device 'SPTI:\Device\CdRom0'
DEBUG: Code 0 at (FS[Bh5JS4pc>jdxo:213130306
DEBUG: Code 0 at <;%3f(R'*M-9Mw'L}6:121264395
DEBUG: Code 4 at <;%3f(R'*M-9Mw'L}6:213130789
003306:0000 Can't read AACS VID from disc - most likely current AACS host certificate is revoked by your drive

You don't need to reflash your drive firmware or make any configuration changes. Powering down your drive completely should sort it out.