BlurayTestAndDecrypt - tool to test bluray files and remove AACS

[nalor]

Originally Posted by LUR

Hi, trying to decrypt Star Wars Disc Collection:

2019-11-26 01:45:33 # 0 # [I] main /  / #############################################################################

2019-11-26 01:45:33 # 0 # [I] main /  /  ----------- BlurayTestAndDecrypt 0.70 ----------- 

2019-11-26 01:45:33 # 55 # [I] SETTINGS / _STG_CreateOrUpdate / Created ini file >C:\Users\LUR\Documents\WORK\BlurayTestAndDecrypt_0.70\BlurayTestAndDecrypt.ini<

2019-11-26 01:45:33 # 55 # [E] common_log / CMLOG_SetLogDirectory / new logdir invalid ><

2019-11-26 01:45:33 # 55 # [I] main /  / Read settings from file >C:\Users\LUR\Documents\WORK\BlurayTestAndDecrypt_0.70\BlurayTestAndDecrypt.ini<

2019-11-26 01:45:33 # 56 # [I] main /  / >> Mode         >0<

2019-11-26 01:45:33 # 56 # [I] main /  / >> DecryptDest  ><

2019-11-26 01:45:33 # 56 # [I] main /  / List of files being processed:

2019-11-26 01:45:33 # 56 # [I] main /  / Detected Drive >D:\<

2019-11-26 01:45:34 # 1643 # [I] main /  / Mode >4< saved in ini-file

2019-11-26 01:45:34 # 1643 # [I] main /  / #############################################################################

2019-11-26 01:45:34 # 1643 # [I] main /  / 1/1 - Srcdrive >D:\< Mode >Decrypt - ContinueOnError<

2019-11-26 01:45:34 # 1649 # [I] main / Bluray_InitDisc / VolumeName: ATTACK_OF_THE_CLONES

2019-11-26 01:45:34 # 1655 # [I] main / Bluray_InitDisc / DiscID:     F08E7A96834680A8BCE152387B9F8594748DA34D

2019-11-26 01:45:34 # 1658 # [I] main / Bluray_InitDisc / Disc is AACS protected - init necessary AACS values

2019-11-26 01:45:34 # 1659 # [I] main / Bluray_InitDisc / Use default AACS-KeyDB file instead >C:\Users\LUR\AppData\Roaming\aacs\keydb.cfg<

2019-11-26 01:45:34 # 1659 # [I] bluray_keydb / BRKDB_OpenFile / KeyDB file >C:\Users\LUR\AppData\Roaming\aacs\keydb.cfg< opened!

2019-11-26 01:45:34 # 1672 # [I] bluray_keydb / BRKDB_OpenFile / KeyDB file >C:\Users\LUR\AppData\Roaming\aacs\keydb.cfg< in memory now

2019-11-26 01:45:36 # 3250 # [I] bluray_keydb / _ParseMem / Removed duplicates for >0< discids from file >C:\Users\LUR\AppData\Roaming\aacs\keydb.cfg<

2019-11-26 01:45:36 # 3250 # [I] bluray_keydb / BRKDB_OpenFile / ParseMem result >1<

2019-11-26 01:45:36 # 3250 # [I] main / Bluray_InitDisc / VUK >9CC0FFB4974AC232B69B2DDEDAABACA2< available in KeyDB entry For disc

2019-11-26 01:45:36 # 3251 # [I] main / Bluray_InitDisc / VUK:        9CC0FFB4974AC232B69B2DDEDAABACA2

2019-11-26 01:45:36 # 3256 # [I] main / Bluray_InitDisc / UnitKeyCnt: 7

2019-11-26 01:45:36 # 3257 # [I] main / Bluray_InitDisc /  >>> UnitKey: 79EC0F4D8A1DFE0E1629116567B48A6B

2019-11-26 01:45:36 # 3257 # [I] main / Bluray_InitDisc /  >>> UnitKey: 85581552DC02679109AF39A4EA5077EB

2019-11-26 01:45:36 # 3258 # [I] main / Bluray_InitDisc /  >>> UnitKey: 53857DE5436B63EFA6BAD7B945433EAF

2019-11-26 01:45:36 # 3258 # [I] main / Bluray_InitDisc /  >>> UnitKey: 671F60BAA4F843411DB18FAB4EA74E1F

2019-11-26 01:45:36 # 3258 # [I] main / Bluray_InitDisc /  >>> UnitKey: 3675EDDA9998DAD0BA5B42C78F9048B9

2019-11-26 01:45:36 # 3259 # [I] main / Bluray_InitDisc /  >>> UnitKey: B9678AAC50E20FFFF706D5CC17C83A41

2019-11-26 01:45:36 # 3259 # [I] main / Bluray_InitDisc /  >>> UnitKey: F3F3C3D750810BC3B9810B6B88967E74

2019-11-26 01:45:36 # 3261 # [I] main / Bluray_InitDisc / Check if disc is BD+ protected

2019-11-26 01:45:36 # 3266 # [I] bluray_aacs / BRAACS_IsBDplusProtected / Directory >D:\BDSVM\< does exist and there is at least 1 .svm file in the folder >00000.svm< - disc is BP+ protected

2019-11-26 01:45:36 # 3266 # [I] main / Bluray_InitDisc / Disc is BD+ protected!

2019-11-26 01:45:36 # 3272 # [I] main / Bluray_InitDisc / BD+ details - Date 2011.07.11 Gen 11

2019-11-26 01:45:38 # 5409 # [I] main / ErrorHandler / A program error was detected:



Error Message:   Invalid memory access

Error Code:      -1073741819

Code Address:    4373540

Target Address:  12

Sourcecode line: 1178

Sourcecode file: U:\PUREBASIC\Bluray-Test\BlurayTest.pb

Will check tonight what is going wrong here...

Gesendet von meinem H8324 mit Tapatalk

[LUR]

Originally Posted by nalor

Will check tonight what is going wrong here...

Gesendet von meinem H8324 mit Tapatalk

How is it going? Any ideas?

[nalor]

I've just uploaded release 0.77 - please try it.

This release includes a few fixes I've done during the last month and maybe your problem is already covered by one of them.

In case it still crashed send me the new report and I'll check the code.

[bleakassassin]

Originally Posted by nalor

I've just uploaded release 0.77 - please try it.

This release includes a few fixes I've done during the last month and maybe your problem is already covered by one of them.

In case it still crashed send me the new report and I'll check the code.

Hi there! I'm not OP, but I'm running into the same issue as that user with the most recent version of this program. I'm trying to decrypt the U.S. release of Birdman, and this is the resulting log. I'd like to note that this occurs both with the disc in my Blu-ray drive and a ripped ISO of it:

2020-04-02 14:31:20 # 0 # [I] main /  / #############################################################################
2020-04-02 14:31:20 # 0 # [I] main /  /  ----------- BlurayTestAndDecrypt 0.77 ----------- 
2020-04-02 14:31:20 # 0 # [I] SETTINGS / _STG_CreateOrUpdate / Created ini file >D:\BlurayTestAndDecrypt_0.77\BlurayTestAndDecrypt.ini<
2020-04-02 14:31:20 # 1 # [E] common_log / CMLOG_SetLogDirectory / new logdir invalid ><
2020-04-02 14:31:20 # 1 # [I] main /  / Read settings from file >D:\BlurayTestAndDecrypt_0.77\BlurayTestAndDecrypt.ini<
2020-04-02 14:31:20 # 74 # [I] main /  / >> Mode         >5<
2020-04-02 14:31:20 # 74 # [I] main /  / >> DecryptDest  >D:\<
2020-04-02 14:31:20 # 75 # [I] bluray_udf / _UDF_Read_MetadataExtendedFileEntry / ++++ Extended File Entry ++++
2020-04-02 14:31:20 # 75 # [I] bluray_udf / _UDF_Parse_FileSetDescriptor / ++++ File Set Descriptor ++++
2020-04-02 14:31:20 # 140 # [I] main /  / List of files being processed:
2020-04-02 14:31:20 # 140 # [I] main /  / Detected File >D:\BlurayTestAndDecrypt_0.77\BIRDMAN.iso<
2020-04-02 14:31:20 # 140 # [I] main /  / #############################################################################
2020-04-02 14:31:20 # 140 # [I] main /  / 1/1 - Decrypt - ISO2ISO >D:\BlurayTestAndDecrypt_0.77\BIRDMAN.iso<
2020-04-02 14:31:20 # 141 # [I] main / CheckAndCreateOutputDir / Decrypt OutputDir: D:\
2020-04-02 14:31:20 # 141 # [I] main / DecryptIso2Iso / UDF - OpenISO
2020-04-02 14:31:20 # 141 # [I] bluray_udf / _UDF_Read_MetadataExtendedFileEntry / ++++ Extended File Entry ++++
2020-04-02 14:31:20 # 141 # [I] bluray_udf / _UDF_Parse_FileSetDescriptor / ++++ File Set Descriptor ++++
2020-04-02 14:31:20 # 203 # [I] main / DecryptIso2Iso / Details about ISO File:
UDF Revision : 0250
VolumeName   : BIRDMAN

2020-04-02 14:31:20 # 203 # [I] main / DecryptIso2Iso / Initialize Disc now
2020-04-02 14:31:20 # 203 # [I] main / Bluray_InitDisc / VolumeName: BIRDMAN
2020-04-02 14:31:20 # 204 # [I] main / Bluray_InitDisc / DiscID:     27245C62EC935F097FC4E4058BA76407E70CEFA2
2020-04-02 14:31:20 # 204 # [I] main / Bluray_InitDisc / Disc is AACS protected - init necessary AACS values
2020-04-02 14:31:20 # 205 # [I] main / Bluray_InitDisc / Use default AACS-KeyDB file instead >C:\Users\Main\AppData\Roaming\aacs\keydb.cfg<
2020-04-02 14:31:20 # 205 # [I] bluray_keydb / BRKDB_OpenFile / KeyDB file >C:\Users\Main\AppData\Roaming\aacs\keydb.cfg< opened!
2020-04-02 14:31:20 # 219 # [I] bluray_keydb / BRKDB_OpenFile / KeyDB file >C:\Users\Main\AppData\Roaming\aacs\keydb.cfg< in memory now
2020-04-02 14:31:22 # 2406 # [I] bluray_keydb / _ParseMem / Removed duplicates for >0< discids from file >C:\Users\Main\AppData\Roaming\aacs\keydb.cfg<
2020-04-02 14:31:22 # 2407 # [I] main / Bluray_InitDisc / VUK >1854B56CA4681135A82C5276BAB03915< available in KeyDB entry for disc
2020-04-02 14:31:22 # 2407 # [I] main / Bluray_InitDisc / VUK:        >1854B56CA4681135A82C5276BAB03915<
2020-04-02 14:31:22 # 2407 # [I] main / Bluray_InitDisc / EncryptedUnitKeyCount >1<
2020-04-02 14:31:22 # 2408 # [I] main / Bluray_InitDisc / UnitKeyCnt: 1
2020-04-02 14:31:22 # 2408 # [I] main / Bluray_InitDisc /  >>> UnitKey: 8ADA030B54AC77C9DE0036497AAA8262
2020-04-02 14:31:22 # 2408 # [I] main / Bluray_InitDisc / Check if disc is BD+ protected
2020-04-02 14:31:22 # 2409 # [I] bluray_aacs / BRAACS_IsBDplusProtected / Directory >\BDSVM< does exist and there is at least 1 .svm file in the folder >\BDSVM\BACKUP\< - disc is BP+ protected
2020-04-02 14:31:22 # 2409 # [I] main / Bluray_InitDisc / Disc is BD+ protected!
2020-04-02 14:31:22 # 2421 # [I] main / Bluray_InitDisc / BD+ details - Date 2014.12.19 Gen 254
2020-04-02 14:31:24 # 4002 # [I] main / ErrorHandler / A program error was detected:

Error Message:   Invalid memory access
Error Code:      -1073741819
Code Address:    1979164744
Target Address:  1
Sourcecode line: 1192
Sourcecode file: U:\PUREBASIC\Bluray-Test\BlurayTest.pb

[nalor]

Released 0.79 - it hopefully fixes the problem reported above (I introduced this bug 2018 ... ) and also changes the way the keydb file is opened: shared readonly, so it's not a problem any longer when the file is also opened in another application in parallel.

[bleakassassin]

That update did the trick. Thanks a ton!

I'm having an issue now with regular usage. Upon getting past that error, I try to advance to decrypting the disc. However, each and every playlist on the disc quickly errors out with the following message:

ERROR! bluray_aacs-BRAACS_AutoDetectUnitKey - Decryption failed with all possible UnitKeys! >1<
ERROR! Couldn't get correct UnitKey!

ERROR! Processing of file >E:\BDMV\STREAM\00xxx.m2ts< failed!

I have an up-to-date keydb.cfg file in my %APPDATA%\aacs folder with the keys from this post added to the top of it. Any idea what's going on?

EDIT: This issue is happening with my retail copy of Birdman (the initial release in the red case). I tried again with Slumdog Millionaire and didn't have any issues.

[Bahamuth]

I have a PAL BluRay from "Pokémon Origins" here. I successfully ripped it with MakeMKV, which lists AACS v63 for the disc.

Just today I read about your program here and decided to test it. But when usind Mode 2 the BluRays ID can't be found in the keydb.cfg (I did download the mentioned file via the information in https://forum.doom9.org/showthread.php?t=176924 and also updated it according to the thread).
Now I wonder how often that keydb.cfg might be updated and what is the best way to do so.

[nateify]

Can anyone re-upload this please? The Tinyupload link appears to be dead

[nalor]

Originally Posted by nateify

Can anyone re-upload this please? The Tinyupload link appears to be dead

Hi!

Updated the link in the first post

[VCL1918]

Hi,
I'm trying to copy some of my Bluray discs to an iso image using Mode 6 (or Mode 7 according to the first post). Unfortunately some of them have special characters (e.g. ":") in their title, which results in an error message like:

11:54:12 - ERROR! -Dump_PrepareDestFile - ERROR! Couldn't create destination file! >C:\Users\Username\Bluray: Disc 1.iso< with size >41.79< GB
11:54:12 - ERROR! -Dump_DumpDrive - ERROR! Couldn't prepare DstFile >C:\Users\Username\Bluray: Disc 1.iso<
11:54:12 - ERROR! DumpDrive >E:\< failed!

Since ":" is not supported in filenames, creating the destination file obviously fails. But afaik it is not possible to set the filename explicitly (only the path).
Any ideas to avoid/fix this?

Thanks in advance,
VCL1918

[nalor]

Originally Posted by VCL1918

Hi,
I'm trying to copy some of my Bluray discs to an iso image using Mode 6 (or Mode 7 according to the first post). Unfortunately some of them have special characters (e.g. ":") in their title, which results in an error message like:

Since ":" is not supported in filenames, creating the destination file obviously fails. But afaik it is not possible to set the filename explicitly (only the path).
Any ideas to avoid/fix this?

Thanks in advance,
VCL1918

Hi! I'm sorry but I missed your post ... today I noticed a problem myself and created an updated release 0.80 and when I wanted to post a message here I noticed your post ... so I've fixed your problem also and now a release 0.81 is available in the first post

[unforeseenconsequences]

I have successfully extracted an .iso using your tool and am trying to use Mode 5 to repair the bdplus (BD+ Gen 7). I have what I believe is the correct convtable in that the filename of the .bin matches my MediaKey. Specifically, the convtable filename is in the format MediaKey_TITLE.bin in the file path %APPDATA%\Roaming\bdplus\convtab\. However, your tool gives me an error of "No matching file found." How exactly does your tool distinguish a convtab "matching file"?

[nalor]

Originally Posted by unforeseenconsequences

I have successfully extracted an .iso using your tool and am trying to use Mode 5 to repair the bdplus (BD+ Gen 7). I have what I believe is the correct convtable in that the filename of the .bin matches my MediaKey. Specifically, the convtable filename is in the format MediaKey_TITLE.bin in the file path %APPDATA%\Roaming\bdplus\convtab\. However, your tool gives me an error of "No matching file found." How exactly does your tool distinguish a convtab "matching file"?

Hi! I just checked the code, the first check is quite simple - the filename has to match the pattern:

"conv_tab_"+sDiscId+"*.bin"

So I guess you're already failing in this situation.

Please try renaming your file and report what happens next

[Bahamuth]

With all cached BD+ tables from https://forum.doom9.org/showthread.php?t=176924 I cannot de-BD+ my Simpsons BluRay. It tells me, that it couldn't find any fitting FixUpTable.

Now I was told, the files inside the conv directory would be named after the MK number, not after the DiscID. So I can't use the cached BD+ tables from the thread then? Does one have to convert/rename them somehow?

[candela]

Originally Posted by Bahamuth

With all cached BD+ tables from https://forum.doom9.org/showthread.php?t=176924 I cannot de-BD+ my Simpsons BluRay. It tells me, that it couldn't find any fitting FixUpTable.

Now I was told, the files inside the conv directory would be named after the MK number, not after the DiscID. So I can't use the cached BD+ tables from the thread then? Does one have to convert/rename them somehow?

simply rename the libaacs file "MK_*.bin" to the format BlurayTestAndDecrypt expects, i.e. "conv_tab_[DiscId]_*.bin" You can find DiscID and MK for your Disc by looking in keydb.cfg, running aacskeys or aacsinfo included with libaacs

[Bahamuth]

Considering there are more BD-J protections than BD+, I wonder if BTAD could also be written to remove such protections? Or is there any other program which reliably remove such things?

[nalor]

Published release 0.94 with a few fixes and a few new features:

use RDK for BusDecryption
when @Candela posted it's message https://forum.doom9.org/showthread.php?t=184373 it's been the first time for me to hear from the ReadDataKey at all.
I started to add the on-the-fly decryption in BTAD and finished it a couple of weeks ago and did not notice any problems in the meantime, so I think its ready for primetime

create BD+ FUT tables with 'mediakey' in name
I wasn't really aware that the files created by BTAD did not match the filenames expected by libbdplus... so I changed it so the filenames are correct now
Additionally I tried XREVEAL and I like it. For an unknown reason it's expecting the BD+ FUT tables in a different directory than libbdplus - so I added the check if XREVEAL is installed and if it is, the FUT file is also created in it's specific directory.
Finally it's working well for me

option for auto-update
It's enabled by default and using the same mechanism as FindVUK - in case a new release is available on the server it get's downloaded and updated. Can be disabled in the ini-file if desired.

A few additional changes are listed on the first post in this thread - and as always it's possible I've introduced new bugs or changed other things without mentioning

[nalor]

Originally Posted by Bahamuth

Considering there are more BD-J protections than BD+, I wonder if BTAD could also be written to remove such protections? Or is there any other program which reliably remove such things?

I can tell that such a thing is way beyond my abilities ...

[Bahamuth]

I have a BluRay here (Resident Evil Degeneration) which is... strange. When I make an encrypted backup with DVDFab, it just rips the BluRay. When I try to make a decrypted backup though, DVDfab fails after 0.55% with a read error.
When I make an decrypted backup with MakeMKV (which doesn't rip to ISO but to the folder structure) I don't get that problem.

When I use BTAD on the image of the encrypted backup, it also stops after 0.55% with this:

16:49:16 - ++ DECODE ++ Pct >  0.54%< StartBlock >00086176< BlockLen >00000723< File >\BDMV\STREAM\00003.m2ts<
16:49:16 - ++  COPY  ++ Pct >  0.55%< StartBlock >00086899< BlockLen >00000013<
16:49:16 - ++ DECODE ++ Pct >  0.55%< StartBlock >00086912< BlockLen >00000240< File >\BDMV\STREAM\00071.m2ts<
16:49:16 - ++  COPY  ++ Pct >  0.55%< StartBlock >00087152< BlockLen >00000016<
16:49:16 - ++ DECODE ++ Pct >  0.55%< StartBlock >00087168< BlockLen >00000270< File >\BDMV\STREAM\00504.m2ts<
           Filename >\BDMV\STREAM\00504.m2ts< Size GB >  0.00< Progress >1/1<

16:49:16 - ERROR! Unencrypted unit has errors! - stop now

The mentioned file is only 540 kB in size and alphabetically is the last in the STREAM folder, but the third when it comes for LBA position. What could be wrong here?

FindVUK doesn't even try any UnitKeys on the file, stopping at this:

17:06:36 - Decrypted first unit of file >D:\BDMV\STREAM\00502.m2ts< with UnitKey >2<
17:06:36 - Decrypted first unit of file >D:\BDMV\STREAM\00503.m2ts< with UnitKey >3<

So I guess it treats the file as unencrypted.

A side note: BTAD blocks access to the keydb.cfg even if it's already done ("Press Escape to exit" is shown).

Another question: are .ssif files encoded on a 3D BluRay? I only noticed BTAD isn't touching them.

[nalor]

Originally Posted by Bahamuth

I have a BluRay here (Resident Evil Degeneration) which is... strange. When I make an encrypted backup with DVDFab, it just rips the BluRay. When I try to make a decrypted backup though, DVDfab fails after 0.55% with a read error.
When I make an decrypted backup with MakeMKV (which doesn't rip to ISO but to the folder structure) I don't get that problem.

When I use BTAD on the image of the encrypted backup, it also stops after 0.55% with this:

16:49:16 - ++ DECODE ++ Pct >  0.54%< StartBlock >00086176< BlockLen >00000723< File >\BDMV\STREAM\00003.m2ts<
16:49:16 - ++  COPY  ++ Pct >  0.55%< StartBlock >00086899< BlockLen >00000013<
16:49:16 - ++ DECODE ++ Pct >  0.55%< StartBlock >00086912< BlockLen >00000240< File >\BDMV\STREAM\00071.m2ts<
16:49:16 - ++  COPY  ++ Pct >  0.55%< StartBlock >00087152< BlockLen >00000016<
16:49:16 - ++ DECODE ++ Pct >  0.55%< StartBlock >00087168< BlockLen >00000270< File >\BDMV\STREAM\00504.m2ts<
           Filename >\BDMV\STREAM\00504.m2ts< Size GB >  0.00< Progress >1/1<

16:49:16 - ERROR! Unencrypted unit has errors! - stop now

The mentioned file is only 540 kB in size and alphabetically is the last in the STREAM folder, but the third when it comes for LBA position. What could be wrong here?

FindVUK doesn't even try any UnitKeys on the file, stopping at this:

17:06:36 - Decrypted first unit of file >D:\BDMV\STREAM\00502.m2ts< with UnitKey >2<
17:06:36 - Decrypted first unit of file >D:\BDMV\STREAM\00503.m2ts< with UnitKey >3<

So I guess it treats the file as unencrypted.

A side note: BTAD blocks access to the keydb.cfg even if it's already done ("Press Escape to exit" is shown).

Another question: are .ssif files encoded on a 3D BluRay? I only noticed BTAD isn't touching them.

Hi!

Have you tried to make an encrypted backup with BTAD? Does this work fine and does the check at the end succeed?

What to you mean with "FindVUK stops" - basically FindVUK only checks if the discovered keys are valid, so as soon as each key has been successfully tested against a single file it's happy as it knows the keys are valid.

Locking of keydb: you're right - will change it in an upcoming release.

And SSIF files are not really separate files on the disc but instead only references to other m2ts files - when you calculate the sum of all files on the disc you'll notice that it won't fit on the disc at all
So when the M2TS files are decoded, the SSIF is automatically decoded as well.

(as far as I remember the SSIF files are the 3d files)