What do I do with an AACS dump?

[koberulz]

Had a failed rip, unknown volume key. Not sure where to send the dump file?

EDIT: Now I'm getting AACS failures for everything, including a disc I successfully ripped five minutes ago. WTF?

[Billycar11]

That's what happens if your drive runs into a disc with a newer aacs version then what makemkv supports.
This does not happen if you have a libredrive drive

[koberulz]

That's what happens if your drive runs into a disc with a newer aacs version then what makemkv supports.

Yes, and my question was where to submit the AACS dump. I remember there being an email address, but not what it is and I can't find it. But that wouldn't explain successfully ripping a disc, then only minutes later having that disc fail to find the AACS key.

I restarted MakeMKV, and everything works fine including the disc that led me to post this thread.

[dcoke22]

Fixing Volume Key is Unknown

[tommik128]

This does not happen if you have a libredrive drive

That is not true. I have a Pioneer 212-EBK in Libre Drive mode (old firmware) backing up blu-rays (not 4ks) and I just got 2 error messages on 2 new movies and back up failed.

I just clicked on that link: Please let us know... assuming it will do what is needed by itself. Also two other movies had this message but succeeded to back up saying Loaded content hash table will verify M2TS files.

[Billycar11]

This does not happen if you have a libredrive drive

That is not true. I have a Pioneer 212-EBK in Libre Drive mode (old firmware) backing up blu-rays (not 4ks) and I just got 2 error messages on 2 new movies and back up failed.

I just clicked on that link: Please let us know... assuming it will do what is needed by itself. Also two other movies had this message but succeeded to back up saying Loaded content hash table will verify M2TS files.

the dev says otherwise...

One famous “feature” of AACS is a so-called host revocation. It was designed to ensure that only “approved” software can use your drive. Every Blu-ray disc contains a file that has a list of host keys known to be used by "unauthorized" software. This list has a version number. The moment you insert the disc into your drive, the drive checks if the list is newer than the one it knows about, and if it is, the drive re-flashes itself (updates firmware). With LibreDrive mode your drive just became immune to this nonsense.

In LibreDrive mode you always would be able to use this drive with MakeMKV or any other software that uses (open source) LibDriveIo library. No AACS revocation or other update would affect usability of your drive in LibreDrive mode.

Please note that LibreDrive mode is not about hacking or meddling with AACS code. In LibreDrive mode the updated software communicates to the drive hardware directly, not touching or hacking AACS DRM code in any way at all. So your drive will continue to self-revoke on MKB updates and require authentication before releasing key material to the "authorized" software - it is just with LibreDrive mode all of it is no longer relevant.

[tommik128]

Strange. I am going to wait a few days and try again.

[tommik128]

So here is the proof: LibreDrive Pioneer, standard blu-ray - not possible to make backup. Should I report this?

Code: Select all

Drive Information
OS device name: E:
Current profile: BD-ROM
Manufacturer: PIONEER
Product: BD-RW BDR-212M
Revision: 1.02
Serial number: xxx
Firmware date: 2022-03-09
Bus encryption flags: 1B
Highest AACS version: 82

LibreDrive Information
Status: Enabled
Drive platform: RS8F00
Firmware name: PIONEER BDR-212T
Firmware type: Original (unpatched)
Firmware version: 1.02/ID56
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

Disc Information
Label: STINY HORKEHO LETA
Timestamp: 2025-08-05 16:59:26
Protection: AACS v82
Data capacity: 21.70 Gb
Disc type: BD-ROM
Number of layers: 1
Channel bit length: 74,5 nm (25.0 GB max. per layer)

https://drive.google.com/file/d/12L1QVX ... sp=sharing
https://drive.google.com/file/d/1YUcPdH ... sp=sharing

[Billycar11]

So here is the proof: LibreDrive Pioneer, standard blu-ray - not possible to make backup. Should I report this?

Code: Select all

Drive Information
OS device name: E:
Current profile: BD-ROM
Manufacturer: PIONEER
Product: BD-RW BDR-212M
Revision: 1.02
Serial number: xxx
Firmware date: 2022-03-09
Bus encryption flags: 1B
Highest AACS version: 82

LibreDrive Information
Status: Enabled
Drive platform: RS8F00
Firmware name: PIONEER BDR-212T
Firmware type: Original (unpatched)
Firmware version: 1.02/ID56
DVD all regions: Yes
BD raw data read: Yes
BD raw metadata read: Yes
Unrestricted read speed: Yes

Disc Information
Label: STINY HORKEHO LETA
Timestamp: 2025-08-05 16:59:26
Protection: AACS v82
Data capacity: 21.70 Gb
Disc type: BD-ROM
Number of layers: 1
Channel bit length: 74,5 nm (25.0 GB max. per layer)

https://drive.google.com/file/d/12L1QVX ... sp=sharing
https://drive.google.com/file/d/1YUcPdH ... sp=sharing

you are miss understanding
yes the newest one wont work until makemkv adds support but your drive is not useless now
if you did not have libredrive your drive would now rip no blurays at all until makemkv added support for the latest aacs

[tommik128]

OK, so even LibreDrive needs support right? I thought it was supposed to automatically bypass that AACS protection.

[keydb_helper]

OK, so even LibreDrive needs support right? I thought it was supposed to automatically bypass that AACS protection.

AACS has multiple layers of encryption. LibreDrive mitigates the outermost layer employed when data is sent from the drive to your CPU. This outermost encryption is called bus encryption and it is performed by licensed drives when reading UHD discs (and certain 1080p discs).

This means LibreDrive will always allow you to make an encrypted backup of any AACS protected disc. This encrypted backup will be an exact copy of the data stored on the disc but it will not be directly playable unless the disc keys can be determined.

Making a decrypted backup of a disc requires additional keys which MakeMKV does not currently bundle for UHD discs or the latest MKBv82 1080p discs.

(If it helps: Imagine you are sending a password protected Microsoft Word file via email. Your email program uses SSL/TLS so the contents of your email are encrypted in transit. Now if someone was able to break or bypass SSL/TLS and intercept the contents of your email they would still have to determine the password for your protected Word file. This scenario is analogous to AACS with SSL/TLS acting as the bus encryption layer and the password protected Word file as the encrypted content on the disc.)

[tommik128]

Thanks for making it 100% clear to me.

Should I email those "MKB_v82" TGZ files from .MakeMKV folder or is it enough when I just click on that link in MakeMKV that says "Please let us know about it by visiting..."?

Since I am using Pioneer drive I cannot contribute to public keydb I guess. Although I have a brand new ASUS BW-16D1HT I bought a few weeks back, so in theory I might change its firmware...

[MrPenguin]

Since I am using Pioneer drive I cannot contribute to public keydb I guess. Although I have a brand new ASUS BW-16D1HT I bought a few weeks back, so in theory I might change its firmware...

I would still recommend contributing your TGZ dump files for ordinary BluRay disks to the public KEYDB, with the possible exception of your drive being a Verbatim 43888 containing a BDR-UD04.

[tommik128]

I would still recommend contributing your TGZ dump files for ordinary Blu-Ray disks to the public KEYDB, with the possible exception of your drive being a Verbatim 43888 containing a BDR-UD04.

It is a 212-EBK (desktop drive, firmware 1.02 / 2022-03-09, LibreDrive Status: Enabled).
So you say for standard full HD blu rays it is fine to upload those TGZ files? I can do that if it makes sense. That guide says no Pioneer drives...

[MrPenguin]

That guide says no Pioneer drives...

Yes, but the guide is also in the "UHD disks" section . To be fair, MakeMKV should only generate a TGZ dump file for an ordinary BluRay using MKBv82.