FindVUK tool - get VUK of all Blurays supported by DVDfab applications

[nalor]

Unfortunately, that's not true.

I'm in the U.S. I can't run DVDFab. All it says is "Sorry, the current disc is protected by AACS." So I have no choice other than to get the VUK manually. Now, I can run MakeMKV -- see the attachment. The MakeMKV log contains the 'discid' (=0xF76764136A8AFD3A999FF1299D4B6044FE90483A), and I find it in the dump of 'makemkvcon64.exe', but where's the VUK? Does anything "few bytes later" look like a VUK to you? How about "few bytes" before? You see, I don't know what I'm looking for other than it is 16 bytes (and it probably isn't populated with a bunch of zeros).

Would you like to take a look at 'makemkvcon64.DMP' to maybe get lucky? It's 578 M-bytes.

I'd really like to support AACS Updater, but this obstacle is pretty much a show stopper.

Regards,
Mark.

Why isn't it possible to run DVDfab in the US? Never thought that it might be a problem... (at least not a technical one).

And the only way to find out if there's something useable in the makemkv dump is by using a disc where you already know the vuk and so you know what you're looking for.
When I initially tried all bluray applications I found on the internet the only one that keeps the vuk easily readable in memory has been DVDfab - but things might have changed in the meantime.

In case DVDfab is really not useable for you I don't know how I could help you...

[candela]

There is no VUK in MakeMKV dumps, don't waste your time. Try using a proxy for DVDFab

[spotter]

I run DVDFab in the US all the time without a problem and without any special tricks.

[Jdogzz]

Below is the log for my attempt to get a VUK. It has been working all morning up until this disc.

2017-06-30 15:49:01 # 152252 # ----------- FindVUK 1.02 -----------
2017-06-30 15:49:01 # 152258 # Operating System: Windows 10
2017-06-30 15:49:01 # 152289 # SettingsFile: >C:\Users\myusername\Downloads\FindVUK_1.02\config\FindVUK.ini<
2017-06-30 15:49:01 # 152309 # Current BufferSize 80 x 300 - ScreenSize 80 x 25
2017-06-30 15:49:01 # 152314 # Requested BufferSize 120 x 300 - ScreenSize 120 x 50
2017-06-30 15:49:01 # 152319 # Max. ScreenSize 240 x 88
2017-06-30 15:49:01 # 152324 # Final New Values - BufferSize 120 x 300 - ScreenSize 120 x 50 - Resize >1<
2017-06-30 15:49:01 # 152328 # M1 - New BufferSize 120 x 300
2017-06-30 15:49:01 # 152333 # Mx2 - New ScreenSize 120 x 50
2017-06-30 15:49:01 # 152347 # Couldn't read PasskeyLogDir from registry - take the info from the ini file
2017-06-30 15:49:01 # 152353 # Information! MediaPlayer MainApp is not valid! ><
2017-06-30 15:49:01 # 152359 # Information! DVDfab MainApp is not valid! ><
2017-06-30 15:49:01 # 152380 # Passkey is preferred and available!
2017-06-30 15:49:01 # 152386 # Passkey-MainFile: >C:\Program Files (x86)\DVDFab Passkey\DVDFabPasskey.exe<
2017-06-30 15:49:01 # 152391 # Passkey-LogFile: >C:\Users\myusername\Documents\DVDFab Passkey\Log\passkey_internal.log<
2017-06-30 15:49:01 # 152396 # KEYDB-Path: >C:\Users\myusername\AppData\Roaming\aacs\<
2017-06-30 15:49:01 # 152402 # KEYDB-Backup-Path: >C:\Users\myusername\Downloads\FindVUK_1.02\VUKbackup\<
2017-06-30 15:49:01 # 152408 # ProcDumpFile: >C:\Users\myusername\Downloads\FindVUK_1.02\tool\procdump.exe<
2017-06-30 15:49:01 # 152414 # --- PART 1 --- GET VUK ---
2017-06-30 15:49:01 # 152425 # Please make sure Passkey is enabled!
2017-06-30 15:49:03 # 154657 # Untested DVDfab App Version found >9.2.0.6<
2017-06-30 15:49:03 # 154662 # Value set in ini file will be used for 'Folder2DiscID'
2017-06-30 15:49:03 # 154667 # Value set in ini file will be used for 'Folder2VUK'
2017-06-30 15:49:03 # 154672 # Offset Folder2DiscId >0x114< - Folder2Vuk >0x173<
2017-06-30 15:49:25 # 177164 # #############################################################################
2017-06-30 15:49:25 # 177172 # ----------- FindVUK 1.02 -----------
2017-06-30 15:49:25 # 177179 # Operating System: Windows 10
2017-06-30 15:49:25 # 177184 # SettingsFile: >C:\Users\myusername\Downloads\FindVUK_1.02\config\FindVUK.ini<
2017-06-30 15:49:25 # 177196 # Current BufferSize 80 x 300 - ScreenSize 80 x 25
2017-06-30 15:49:25 # 177201 # Requested BufferSize 120 x 300 - ScreenSize 120 x 50
2017-06-30 15:49:25 # 177206 # Max. ScreenSize 240 x 88
2017-06-30 15:49:25 # 177210 # Final New Values - BufferSize 120 x 300 - ScreenSize 120 x 50 - Resize >1<
2017-06-30 15:49:25 # 177215 # M1 - New BufferSize 120 x 300
2017-06-30 15:49:25 # 177221 # Mx2 - New ScreenSize 120 x 50
2017-06-30 15:49:25 # 177234 # Couldn't read PasskeyLogDir from registry - take the info from the ini file
2017-06-30 15:49:25 # 177241 # Information! MediaPlayer MainApp is not valid! ><
2017-06-30 15:49:26 # 177247 # Information! DVDfab MainApp is not valid! ><
2017-06-30 15:49:26 # 177264 # Passkey is preferred and available!
2017-06-30 15:49:26 # 177269 # Passkey-MainFile: >C:\Program Files (x86)\DVDFab Passkey\DVDFabPasskey.exe<
2017-06-30 15:49:26 # 177274 # Passkey-LogFile: >C:\Users\myusername\Documents\DVDFab Passkey\Log\passkey_internal.log<
2017-06-30 15:49:26 # 177280 # KEYDB-Path: >C:\Users\myusername\AppData\Roaming\aacs\<
2017-06-30 15:49:26 # 177285 # KEYDB-Backup-Path: >C:\Users\myusername\Downloads\FindVUK_1.02\VUKbackup\<
2017-06-30 15:49:26 # 177291 # ProcDumpFile: >C:\Users\myusername\Downloads\FindVUK_1.02\tool\procdump.exe<
2017-06-30 15:49:26 # 177297 # --- PART 1 --- GET VUK ---
2017-06-30 15:49:26 # 177308 # No running application process discovered
2017-06-30 15:49:26 # 177313 # >> Start it now >C:\Program Files (x86)\DVDFab Passkey\DVDFabPasskey.exe<
2017-06-30 15:49:28 # 180208 # Untested DVDfab App Version found >9.2.0.6<
2017-06-30 15:49:28 # 180213 # Value set in ini file will be used for 'Folder2DiscID'
2017-06-30 15:49:28 # 180218 # Value set in ini file will be used for 'Folder2VUK'
2017-06-30 15:49:28 # 180223 # Offset Folder2DiscId >0x114< - Folder2Vuk >0x173<
2017-06-30 15:49:33 # 184803 # Drive opened
2017-06-30 15:49:33 # 184809 # DiscType detected >Blu-ray BDMV<
2017-06-30 15:49:33 # 184816 # Volume Label detected >AMAZING_SPIDERMAN<
2017-06-30 15:49:33 # 184822 # DriveLetter detected >D<
2017-06-30 15:49:34 # 185536 # Detected CopyProtections AACS >1< BD+ >0<
2017-06-30 15:49:42 # 193631 # DiscID found >BEF7D426F926398B33D1BF7E7F5181061B8B3374<
2017-06-30 15:49:43 # 194751 # Passkey got VUK - create memdump now!
2017-06-30 15:49:44 # 195501 # DUMP >>>
2017-06-30 15:49:44 # 195509 # DUMP >>> ProcDump v9.0 - Sysinternals process dump utility
2017-06-30 15:49:44 # 195515 # DUMP >>> Copyright (C) 2009-2017 Mark Russinovich and Andrew Richards
2017-06-30 15:49:44 # 195521 # DUMP >>> Sysinternals - www.sysinternals.com
2017-06-30 15:49:44 # 195528 # DUMP >>>
2017-06-30 15:49:44 # 195535 # DUMP >>> [15:49:44] Dump 1 initiated: C:\Users\myusername\Downloads\FindVUK_1.02\dump\BEF7D426F926398B33D1BF7E7F5181061B8B3374_AMAZING_S7412ERMAN.dmp
2017-06-30 15:49:44 # 196147 # DUMP >>> [15:49:44] Dump 1 writing: Estimated dump file size is 122 MB.
2017-06-30 15:49:49 # 200296 # DUMP >>> [15:49:49] Dump 1 complete: 122 MB written in 4.8 seconds
2017-06-30 15:49:49 # 200604 # DUMP >>> [15:49:49] Waiting for dump to complete...
2017-06-30 15:49:49 # 200812 # DUMP >>> [15:49:49] Dump count reached.
2017-06-30 15:49:49 # 200817 # DUMP >>>
2017-06-30 15:49:49 # 200923 # ERROR!! Dumpsize invalid >-1< - Exitcode >1< - Dump failed! - Program >C:\Users\myusername\Downloads\FindVUK_1.02\tool\procdump.exe< Parameter > -ma -o DVDFabPasskey.exe "C:\Users\myusername\Downloads\FindVUK_1.02\dump\BEF7D426F926398B33D1BF7E7F5181061B8B3374_AMAZING_SPIDERMAN.dmp"<
2017-06-30 15:49:49 # 200929 # Error during process memory dump - please report in the doom9 forum!
2017-06-30 15:49:49 # 200936 # ERROR! Couldn't create memory dump! Exit application!
2017-06-30 15:49:49 # 200948 # CloseAtTheEnd is active, close Passkey now

[Jdogzz]

Two more dump errors:

2017-06-30 16:08:38 # 1330339 # ----------- FindVUK 1.02 -----------
2017-06-30 16:08:38 # 1330346 # Operating System: Windows 10
2017-06-30 16:08:38 # 1330351 # SettingsFile: >C:\Users\myusername\Downloads\FindVUK_1.02\config\FindVUK.ini<
2017-06-30 16:08:38 # 1330366 # Current BufferSize 80 x 300 - ScreenSize 80 x 25
2017-06-30 16:08:38 # 1330372 # Requested BufferSize 120 x 300 - ScreenSize 120 x 50
2017-06-30 16:08:38 # 1330378 # Max. ScreenSize 240 x 88
2017-06-30 16:08:38 # 1330385 # Final New Values - BufferSize 120 x 300 - ScreenSize 120 x 50 - Resize >1<
2017-06-30 16:08:38 # 1330392 # M1 - New BufferSize 120 x 300
2017-06-30 16:08:38 # 1330398 # Mx2 - New ScreenSize 120 x 50
2017-06-30 16:08:38 # 1330433 # Couldn't read PasskeyLogDir from registry - take the info from the ini file
2017-06-30 16:08:38 # 1330444 # Information! MediaPlayer MainApp is not valid! ><
2017-06-30 16:08:38 # 1330452 # Information! DVDfab MainApp is not valid! ><
2017-06-30 16:08:38 # 1330458 # Passkey is preferred and available!
2017-06-30 16:08:38 # 1330463 # Passkey-MainFile: >C:\Program Files (x86)\DVDFab Passkey\DVDFabPasskey.exe<
2017-06-30 16:08:38 # 1330468 # Passkey-LogFile: >C:\Users\myusername\Documents\DVDFab Passkey\Log\passkey_internal.log<
2017-06-30 16:08:38 # 1330473 # KEYDB-Path: >C:\Users\myusername\AppData\Roaming\aacs\<
2017-06-30 16:08:38 # 1330478 # KEYDB-Backup-Path: >C:\Users\myusername\Downloads\FindVUK_1.02\VUKbackup\<
2017-06-30 16:08:38 # 1330483 # ProcDumpFile: >C:\Users\myusername\Downloads\FindVUK_1.02\tool\procdump.exe<
2017-06-30 16:08:38 # 1330489 # --- PART 1 --- GET VUK ---
2017-06-30 16:08:38 # 1330499 # No running application process discovered
2017-06-30 16:08:38 # 1330504 # >> Start it now >C:\Program Files (x86)\DVDFab Passkey\DVDFabPasskey.exe<
2017-06-30 16:08:41 # 1332839 # Untested DVDfab App Version found >9.2.0.6<
2017-06-30 16:08:41 # 1332845 # Value set in ini file will be used for 'Folder2DiscID'
2017-06-30 16:08:41 # 1332851 # Value set in ini file will be used for 'Folder2VUK'
2017-06-30 16:08:41 # 1332857 # Offset Folder2DiscId >0x114< - Folder2Vuk >0x173<
2017-06-30 16:08:49 # 1341557 # Drive opened
2017-06-30 16:08:49 # 1341566 # DiscType detected >Blu-ray BDMV<
2017-06-30 16:08:49 # 1341575 # Volume Label detected >The Amazing Spider-Man<
2017-06-30 16:08:51 # 1343402 # DriveLetter detected >D<
2017-06-30 16:08:53 # 1345631 # Detected CopyProtections AACS >1< BD+ >0<
2017-06-30 16:09:10 # 1362111 # DiscID found >C4D07F0A46D53D68C4F450E71F939921AC852536<
2017-06-30 16:09:11 # 1363533 # Passkey got VUK - create memdump now!
2017-06-30 16:09:11 # 1363640 # DUMP >>>
2017-06-30 16:09:11 # 1363646 # DUMP >>> ProcDump v9.0 - Sysinternals process dump utility
2017-06-30 16:09:11 # 1363653 # DUMP >>> Copyright (C) 2009-2017 Mark Russinovich and Andrew Richards
2017-06-30 16:09:11 # 1363658 # DUMP >>> Sysinternals - www.sysinternals.com
2017-06-30 16:09:11 # 1363664 # DUMP >>>
2017-06-30 16:09:11 # 1363670 # DUMP >>> [16:09:11] Dump 1 initiated: C:\Users\myusername\Downloads\FindVUK_1.02\dump\C4D07F0A46D53D68C4F450E71F939921AC852536_The_Amazing_S5508er-Man.dmp
2017-06-30 16:09:11 # 1363676 # DUMP >>> [16:09:11] Dump 1 writing: Estimated dump file size is 126 MB.
2017-06-30 16:09:12 # 1363884 # DUMP >>> [16:09:12] Dump 1 complete: 126 MB written in 0.2 seconds
2017-06-30 16:09:12 # 1364093 # DUMP >>> [16:09:12] Dump count reached.
2017-06-30 16:09:12 # 1364099 # DUMP >>>
2017-06-30 16:09:12 # 1364107 # ERROR!! Dumpsize invalid >-1< - Exitcode >1< - Dump failed! - Program >C:\Users\myusername\Downloads\FindVUK_1.02\tool\procdump.exe< Parameter > -ma -o DVDFabPasskey.exe "C:\Users\myusername\Downloads\FindVUK_1.02\dump\C4D07F0A46D53D68C4F450E71F939921AC852536_The_Amazing_Spider-Man.dmp"<
2017-06-30 16:09:12 # 1364114 # Error during process memory dump - please report in the doom9 forum!
2017-06-30 16:09:12 # 1364122 # ERROR! Couldn't create memory dump! Exit application!
2017-06-30 16:09:12 # 1364135 # CloseAtTheEnd is active, close Passkey now
2017-06-30 16:10:13 # 1425165 # #############################################################################
2017-06-30 16:10:13 # 1425173 # ----------- FindVUK 1.02 -----------
2017-06-30 16:10:13 # 1425180 # Operating System: Windows 10
2017-06-30 16:10:13 # 1425186 # SettingsFile: >C:\Users\myusername\Downloads\FindVUK_1.02\config\FindVUK.ini<
2017-06-30 16:10:13 # 1425198 # Current BufferSize 80 x 300 - ScreenSize 80 x 25
2017-06-30 16:10:13 # 1425203 # Requested BufferSize 120 x 300 - ScreenSize 120 x 50
2017-06-30 16:10:13 # 1425207 # Max. ScreenSize 240 x 88
2017-06-30 16:10:13 # 1425213 # Final New Values - BufferSize 120 x 300 - ScreenSize 120 x 50 - Resize >1<
2017-06-30 16:10:13 # 1425217 # M1 - New BufferSize 120 x 300
2017-06-30 16:10:13 # 1425222 # Mx2 - New ScreenSize 120 x 50
2017-06-30 16:10:13 # 1425236 # Couldn't read PasskeyLogDir from registry - take the info from the ini file
2017-06-30 16:10:13 # 1425243 # Information! MediaPlayer MainApp is not valid! ><
2017-06-30 16:10:13 # 1425250 # Information! DVDfab MainApp is not valid! ><
2017-06-30 16:10:13 # 1425264 # Passkey is preferred and available!
2017-06-30 16:10:13 # 1425269 # Passkey-MainFile: >C:\Program Files (x86)\DVDFab Passkey\DVDFabPasskey.exe<
2017-06-30 16:10:13 # 1425275 # Passkey-LogFile: >C:\Users\myusername\Documents\DVDFab Passkey\Log\passkey_internal.log<
2017-06-30 16:10:13 # 1425280 # KEYDB-Path: >C:\Users\myusername\AppData\Roaming\aacs\<
2017-06-30 16:10:13 # 1425285 # KEYDB-Backup-Path: >C:\Users\myusername\Downloads\FindVUK_1.02\VUKbackup\<
2017-06-30 16:10:13 # 1425291 # ProcDumpFile: >C:\Users\myusername\Downloads\FindVUK_1.02\tool\procdump.exe<
2017-06-30 16:10:13 # 1425297 # --- PART 1 --- GET VUK ---
2017-06-30 16:10:13 # 1425306 # No running application process discovered
2017-06-30 16:10:13 # 1425312 # >> Start it now >C:\Program Files (x86)\DVDFab Passkey\DVDFabPasskey.exe<
2017-06-30 16:10:16 # 1427918 # Untested DVDfab App Version found >9.2.0.6<
2017-06-30 16:10:16 # 1427924 # Value set in ini file will be used for 'Folder2DiscID'
2017-06-30 16:10:16 # 1427929 # Value set in ini file will be used for 'Folder2VUK'
2017-06-30 16:10:16 # 1427933 # Offset Folder2DiscId >0x114< - Folder2Vuk >0x173<
2017-06-30 16:10:50 # 1461995 # Drive opened
2017-06-30 16:10:50 # 1462002 # DiscType detected >Blu-ray BDMV<
2017-06-30 16:10:50 # 1462010 # Volume Label detected >The Amazing Spider-Man 2<
2017-06-30 16:10:50 # 1462119 # DriveLetter detected >D<
2017-06-30 16:10:51 # 1463538 # Detected CopyProtections AACS >1< BD+ >0<
2017-06-30 16:10:57 # 1469694 # DiscID found >DE3D6C9EF713E0507924DB9C35F0BF7EA258E958<
2017-06-30 16:10:59 # 1470915 # Passkey got VUK - create memdump now!
2017-06-30 16:10:59 # 1471022 # DUMP >>>
2017-06-30 16:10:59 # 1471028 # DUMP >>> ProcDump v9.0 - Sysinternals process dump utility
2017-06-30 16:10:59 # 1471034 # DUMP >>> Copyright (C) 2009-2017 Mark Russinovich and Andrew Richards
2017-06-30 16:10:59 # 1471040 # DUMP >>> Sysinternals - www.sysinternals.com
2017-06-30 16:10:59 # 1471047 # DUMP >>>
2017-06-30 16:10:59 # 1471053 # DUMP >>> [16:10:59] Dump 1 initiated: C:\Users\myusername\Downloads\FindVUK_1.02\dump\DE3D6C9EF713E0507924DB9C35F0BF7EA258E958_The_Amazing_S7844er-Man_2.dmp
2017-06-30 16:10:59 # 1471059 # DUMP >>> [16:10:59] Dump 1 writing: Estimated dump file size is 123 MB.
2017-06-30 16:10:59 # 1471165 # DUMP >>> [16:10:59] Dump 1 complete: 123 MB written in 0.2 seconds
2017-06-30 16:10:59 # 1471475 # DUMP >>> [16:10:59] Dump count reached.
2017-06-30 16:10:59 # 1471480 # DUMP >>>
2017-06-30 16:10:59 # 1471486 # ERROR!! Dumpsize invalid >-1< - Exitcode >1< - Dump failed! - Program >C:\Users\myusername\Downloads\FindVUK_1.02\tool\procdump.exe< Parameter > -ma -o DVDFabPasskey.exe "C:\Users\myusername\Downloads\FindVUK_1.02\dump\DE3D6C9EF713E0507924DB9C35F0BF7EA258E958_The_Amazing_Spider-Man_2.dmp"<
2017-06-30 16:10:59 # 1471491 # Error during process memory dump - please report in the doom9 forum!
2017-06-30 16:10:59 # 1471497 # ERROR! Couldn't create memory dump! Exit application!
2017-06-30 16:10:59 # 1471507 # CloseAtTheEnd is active, close Passkey now

[Jdogzz]

My apologies, I read through some of the earlier replies and saw you need the dumps produced as well. Here is a folder on Mediafire for the dumps (there are some duplicates for the first error I reported) :
https://www.mediafire.com/folder/ciythk79tm70t/Failed_Dumps

[nalor]

This is funny - FindVUK is stumbling across a new feature in procdump since release 8.2:

ProcDump Webpage (https://technet.microsoft.com/en-us/sysinternals/dd996900)

Filename:

Default dump filename: PROCESSNAME_YYMMDD_HHMMSS.dmp

The following substitutions are supported:
PROCESSNAME Process Name
PID Process ID
EXCEPTIONCODE Exception Code
HHMMSS Hour/Minute/Second

so whenever there's PID (like in sPIDerman) in the dump filename it get's replaced by the process-id of the process that is dumped ...

I cannot find a parameter to disable this behaviour, so I'll simply replace all 'pid' with 'pi_d' or something like this in the next release of FindVUK.

Short term solution: download an older release of procdump (a release before 8.2 - e.g. 8.0 is a good one)

[nalor]

My apologies, I read through some of the earlier replies and saw you need the dumps produced as well. Here is a folder on Mediafire for the dumps (there are some duplicates for the first error I reported) :
https://www.mediafire.com/folder/ciythk79tm70t/Failed_Dumps

In this case it's not necessary - I noticed the weird filename used by procdump when I first read your post, but I've been clueless until I tried myself to create a dump with destination filename 'spiderman' and noticed that I can reproduce your problem quite easily ;)

[Jdogzz]

@nalor: Your suggestion for using an older procdump executable worked, thanks!

PS: For anyone else having this problem (looks like @wuemura might have: https://forum.doom9.org/showthread.php?p=1809782#post1809782 ), it appears that MS, in their infinite wisdom because new versions of their products definitely will never lead to bugs, does not host old versions of their tools. I found a copy of version 8.0 on Internet Archive here: https://web.archive.org/web/20160708090036/https://download.sysinternals.com/files/Procdump.zip .

[LM2005]

@nalor: Your suggestion for using an older procdump executable worked, thanks!

PS: For anyone else having this problem (looks like @wuemura might have: https://forum.doom9.org/showthread.php?p=1809782#post1809782 ), it appears that MS, in their infinite wisdom because new versions of their products definitely will never lead to bugs, does not host old versions of their tools. I found a copy of version 8.0 on Internet Archive here: https://web.archive.org/web/20160708090036/https://download.sysinternals.com/files/Procdump.zip .
You are talking about a big organization, they are born sick.
However there is a Power tool called procdump v9.0, would that work. It was started by Mark Russinovich, who seemed to be a competent man.
https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx I once used their forum and people there were helpfull.

[xplt]

Hi nalor!
I think, I encountered a bug in FindVUK: a few days ago I re-installed Windows on a machine which I use to extract keys and I created a user with Cyrillic name (so, path to user files has both Latin and Cyrillic characters). And for some reason, FindVUK doesn't like Cyrillic for "DVDfab-LogFile" (and other files) while it is able to decode it for "KEYDB-Path". See the attached log.

[nalor]

Please upload the logfile e.g. to tinyupload or paste it on pastebin.com
alternatively post the path incl. the cyrillic name here

thanks!

[xplt]

Please upload the logfile e.g. to tinyupload or paste it on pastebin.com
alternatively post the path incl. the cyrillic name here

thanks!

Uploaded on pastebin (https://pastebin.com/8TvL6ZSa).

[nalor]

Interesting, will try it tonight with your username.

Gesendet von meinem E5823 mit Tapatalk

[ErichV]

Hi nalor,
Could you please add support for DVDFab Media Player 3.1.0.2 in the next FindVUK release?
Thank you very much for all your efforts! :-)

[nalor]

Uploaded on pastebin (https://pastebin.com/8TvL6ZSa).

Took a little bit longer than expected, but I've tried it with your username now and unfortunately it's not the fault of FindVUK.

The main problem is that DVDfab does not handle the special username properly and fails to write to it's default directory in the 'documents' folder inside the user directory >> in my case it created the logfile directly in the 'C:\Users' folder and as usually only the admin is allowed to write to this folder, I have to start DVDfab with admin rights to get it running.

You can specify the logpath in the ini file of FindVUK - so in my case I've changed it to 'C:\Users\DVDFab10\Log\dvdfab_internal.log' and it worked even with your username (but note that I had to start FindVUK also with admin-rights so it can start DVDfab with admin rights.. )

Finally it's working - but I don't think it's a good solution, better to use an easier username ;)

[nalor]

Hi nalor,
Could you please add support for DVDFab Media Player 3.1.0.2 in the next FindVUK release?
Thank you very much for all your efforts! :-)

Already implemented it a while ago - but as nobody complained I resigned to release it.
Will try to create a new release this weekend.

[ErichV]

Will try to create a new release this weekend.

Awesome, thanks a lot.

[nalor]

Awesome, thanks a lot.

I'm sorry but I will not make it this weekend.

There's one new feature I'd like to finish before releasing a new version:

I'd like to create an alternative to Starbucks AACS-Database that is able to store all information we can get from the dumps and also is available more or less immediatly after upload.
But I'm still in the early stages of this project.. and don't think I can finish it today.

And another bad news: I noticed that beginning with Passkey 9.2.1.2 and DVDfab 10.0.4.9 the VUK is now encrypted in memory - so for the moment please use older releases to get valid VUKs.
(but there won't be solution for this in the next release as I don't know how to decrypt the VUK in the new releases ... )

But I'll add an error message in the next release telling you that the new releases are not supported any longer :(

[m4tthi4s]

And another bad news: I noticed that beginning with Passkey 9.2.1.2 and DVDfab 10.0.4.9 the VUK is now encrypted in memory - so for the moment please use older releases to get valid VUKs.
(but there won't be solution for this in the next release as I don't know how to decrypt the VUK in the new releases ... )

Do you have more information? How did you find out that it is encrypted?

[candela]

Do you have more information? How did you find out that it is encrypted?

I think "encrypted" is the wrong choice of words. The keys are no longer available at fixed offsets and the presence of keys also seems to depends on the timing of the dump. It doesn't seem like they are actively trying to hide keys though. Even a simple xor would make us find nothing. I don't remember if previously the unitkeys were present but now they are. So possibly they just changed some code which has some bad side effects for us. Judging from a couple of tests, most if not all keys are still present when the dump is taken at the right time but at semi-random locations.

Brute force is a way to get keys from the dump but each key requires a different kind of verification and is obviously more time consuming then dumping data at fixed offsets. However, such a general implementation would also work with dumps from other rippers/players that have at least title keys (Leawo, etc.) so the effort seems worthwhile

[nalor]

I think the memory area we're usually searching for is a c-structure - and that the relevant information (volumeid, mediakey, vuk) is still there, but not in plaintext any longer... I also noticed that the beginning of the structure is different now, so basically it might be possible to detect if it's a plaintext structure or an obfuscated one without even validating the vuk, but for the moment I'll just check the version of DVDfab and Passkey and exit in case an unsupported version is discovered.

If anyone is interested: I already created a brute-force application that is simply searching for a valid VUK in a memory dump - using 4 threads that check simultaneously it takes about 2min to check all possible combinations in a 100mb binary file and personally I've no idea how I could optimize this any further (AES encoding / decoding is already done with libgcrypt because the internal purebasic methods are way too slow) and with 4 threads my cpu is already on it's limit.

So for the moment it's easier to use an older release of the dvdfab applications (and I can install different releases without restarting windows - so I think it's no problem at all to switch to an older release for FindVUK and install the current one again afterwards).

[ErichV]

Already implemented it a while ago - but as nobody complained I resigned to release it.
Will try to create a new release this weekend.

FYI:
A new version of DVDFab Media Player has been released: 3.2.0.0

[spotter]

recently upgraded to 17.09 windows 10 release, and findvuk is now failing on the dump

2017-12-04 17:35:43 # 173312 # DiscID found >607675E3ECDCC36202EADC0BC85A5B34337D1C33<
2017-12-04 17:35:44 # 174627 # DVDfab got VUK - create memdump now!
2017-12-04 17:35:44 # 174734 # DUMP >>>
2017-12-04 17:35:44 # 174740 # DUMP >>> ProcDump v9.0 - Sysinternals process dump utility
2017-12-04 17:35:44 # 174745 # DUMP >>> Copyright (C) 2009-2017 Mark Russinovich and Andrew Richards
2017-12-04 17:35:44 # 174752 # DUMP >>> Sysinternals - www.sysinternals.com
2017-12-04 17:35:44 # 174757 # DUMP >>>
2017-12-04 17:35:44 # 174762 # DUMP >>> [17:35:44] Multiple processes match the specified name.
2017-12-04 17:35:44 # 174769 # ERROR!! Exitcode >-2< - Dump failed! - Program >C:\Users\spott\Downloads\FindVUK_1.02\tool\procdump.exe< Parameter > -ma -o DVDFab.exe "C:\Users\spott\Downloads\FindVUK_1.02\dump\607675E3ECDCC36202EADC0BC85A5B34337D1C33_HOUSE_OF_CARDS_TRILOGY_D1.dmp"<
2017-12-04 17:35:44 # 174775 # Error during process memory dump - please report in the doom9 forum!
2017-12-04 17:35:44 # 174785 # ERROR! Couldn't create memory dump! Exit application!
2017-12-04 17:35:44 # 174795 # CloseAtTheEnd is active, close DVDfab now
2017-12-04 17:35:44 # 174805 # There are >1< DVDfab processes running

[spotter]

if I run procdump manually, the same thing happens, but if I run it with the pid of the dvdfab process, it works.

It be nice if findvuk could be updated to use pid instead of just the exe name.

[nalor]

if I run procdump manually, the same thing happens, but if I run it with the pid of the dvdfab process, it works.

It be nice if findvuk could be updated to use pid instead of just the exe name.Interesting, upgraded my Computer also to 1709 on saturday and used findvuk yesterday without any problems.
Will check tonight which exact version of procdump I am using and will also check with your version.

Gesendet von meinem E5823 mit Tapatalk

[spotter]

Interesting, upgraded my Computer also to 1709 on saturday and used findvuk yesterday without any problems.
Will check tonight which exact version of procdump I am using and will also check with your version.

Gesendet von meinem E5823 mit Tapatalk

I was able to run procdump by name on notepad.exe, maybe a function of something else, but as I said, pid worked fine. if you exec the dvdfab product, you should have the pid, right?

[hajj_3]

DVDFab Media Player 3.2.0.1 has been released.

[nalor]

2017-12-04 17:35:44 # 174762 # DUMP >>> [17:35:44] Multiple processes match the specified name.

Just noticed this line and I think it explains why it didn't work -> it seems as if 2 dvdfab processes were running at the same time?

Unfortunately I don't get the PID when I start something with FindVUK - so all I could do is to retrieve it later and would also fail because I couldn't identify the correct process in case there are multiple running with the same name.

So for the moment I think I'll just keep it as it is.

[ErichV]

FYI: DVDFab Media Player 5.0.0.1 has been released.

[nalor]

FYI: DVDFab Media Player 5.0.0.1 has been released.Will try to check it during the christmas holidays :-)

Gesendet von meinem E5823 mit Tapatalk

[nalor]

New release 1.05 is now online - the list of new features is not that impressive:

# read Mainplaylist from passkey-log and dvdfab-log and write it to a 'bluraydb-file' (just a test file in the user directory)
# support for DVDfab until 10.0.4.8 and Mediaplayer 3.2.0.0
>> newer releases are not supported any longer
# new mode /synchronize that synchronizes with an online database - the url currently written to the ini-file 'http://fvonline-db.bplaced.net' is just a dummy website - there's a static keydb file available for download and uploads are possible, but there's no backend that processes them -> currently I think Relight will help here, see New Online Database (https://forum.doom9.org/showthread.php?t=175194)
# new mode /GetMetaInfoFromDisc=X - just collects meta information from this inserted in drive X and uploads it to the new online database

All in all not that impressive... and finally I have to admit that as always I haven't done that much testing with the new release....

I've just tested the main function - extract the VUK from a memory dump - with Passkey and DVDfab and it's working as expected.

But everything else is more or less untested....

You can get the release here: FindVUK 1.05 (http://s000.tinyupload.com/index.php?file_id=06983443627255430265)

[ErichV]

It looks like version 1.05 is not able to add new keys to the keydb.cfg file.
However, determining the VUK works fine with Mediaplayer 3.2.0.0.

[nalor]

It looks like version 1.05 is not able to add new keys to the keydb.cfg file.
However, determining the VUK works fine with Mediaplayer 3.2.0.0.Can you upload the log with the error to tinyupload?
What I remember I have not changed the related code...

Gesendet von meinem E5823 mit Tapatalk

[candela]

Some issues in 1.05:

- new UnitKeys are not written when there's already an entry for the DiscID in main/backup keydb

- when re-opening the same disc without closing MediaPlayer, the entry is always written even though the same entry already exists. Also the database upload fails then


22:43:00 - -------------------------------------------------------
22:43:00 - --- Write entry in main-keydb file ---
22:43:00 - -------------------------------------------------------
22:43:00 - Keys in Keyfile: 0 keys - KeyFile: C:\Users\\AppData\Roaming\aacs\KEYDB.cfg
22:43:00 - KEYDB: no entry found for disc >> write new entry in keydb-file
22:43:00 - Added line with VUK to file >C:\Users\\AppData\Roaming\aacs\KEYDB.cfg<

22:43:00 - -------------------------------------------------------
22:43:00 - --- Write entry in backup-keydb file ---
22:43:00 - -------------------------------------------------------
22:43:00 - Keys in Keyfile: 0 keys - KeyFile: C:\Utils\FindVUK_1.05\VUKbackup\KEYDB.cfg
22:43:00 - KEYDB: no entry found for disc >> write new entry in keydb-file
22:43:00 - Added line with VUK to backup-file >C:\Utils\FindVUK_1.05\VUKbackup\KEYDB.cfg<
22:43:00 - ERROR! Couldn't post the BlurayMetaXML to the OnlineDB! (http://fvonline-db.bplaced.net/fv_upload.php) >< (0)

- md5 hash is lowercase (not really a bug)

- with AacsUpdater out of the picture, isn't it better to enable saving of all keys in keydb by default. At least in the keydb backup file

[ErichV]

...EVERYTHING IS FINE UP TO THIS POINT...

2018-01-23 23:41:32 # 759810 # [I] main / legacy / -------------------------------------------------------
2018-01-23 23:41:32 # 759811 # [I] main / legacy / -------------------------------------------------------
2018-01-23 23:41:32 # 759811 # [I] main / legacy / --- Write entry in main-keydb file ---
2018-01-23 23:41:32 # 759811 # [I] main / legacy / -------------------------------------------------------

... followed by several entries like this one ...

2018-01-23 23:41:32 # 760216 # [E] bluray_keydb / _DebugDifference / DiscIDx1/0 - Title1 >y1< Title2 >z1<
2018-01-23 23:41:32 # 760480 # [E] bluray_keydb / _DebugDifference / DiscIDx2/0 - Title1 >y2< Title2 >z2<
...

Then, FindVUK suddenly stops without any error message.

[nalor]

Some issues in 1.05:

- new UnitKeys are not written when there's already an entry for the DiscID in main/backup keydb

- when re-opening the same disc without closing MediaPlayer, the entry is always written even though the same entry already exists. Also the database upload fails then


22:43:00 - -------------------------------------------------------
22:43:00 - --- Write entry in main-keydb file ---
22:43:00 - -------------------------------------------------------
22:43:00 - Keys in Keyfile: 0 keys - KeyFile: C:\Users\\AppData\Roaming\aacs\KEYDB.cfg
22:43:00 - KEYDB: no entry found for disc >> write new entry in keydb-file
22:43:00 - Added line with VUK to file >C:\Users\\AppData\Roaming\aacs\KEYDB.cfg<

22:43:00 - -------------------------------------------------------
22:43:00 - --- Write entry in backup-keydb file ---
22:43:00 - -------------------------------------------------------
22:43:00 - Keys in Keyfile: 0 keys - KeyFile: C:\Utils\FindVUK_1.05\VUKbackup\KEYDB.cfg
22:43:00 - KEYDB: no entry found for disc >> write new entry in keydb-file
22:43:00 - Added line with VUK to backup-file >C:\Utils\FindVUK_1.05\VUKbackup\KEYDB.cfg<
22:43:00 - ERROR! Couldn't post the BlurayMetaXML to the OnlineDB! (http://fvonline-db.bplaced.net/fv_upload.php) >< (0)

- md5 hash is lowercase (not really a bug)

- with AacsUpdater out of the picture, isn't it better to enable saving of all keys in keydb by default. At least in the keydb backup file

Question:
when is the download url used?

Will check tomorrow, but I think you're right - I will remove the settings to enable/disable the saving of different elements into keydb.cfg and enable all of them by default.

The upload into the url that is currently set in the ini file always includes all details and as soon as the database of @Relight is functional I will re-poste all uploads that got uploaded into the interims database to his database.

[candela]

Can you read your PM asap please, i possibly uploaded things i shouldn't have ;)

Also you can keep the settings, just put the default value to 1=enabled

[nalor]

...EVERYTHING IS FINE UP TO THIS POINT...

[CODE]2018-01-23 23:41:32 # 760216 # [E] bluray_keydb / _DebugDifference / DiscIDx1/0 - Title1 >y1< Title2 >z1<
2018-01-23 23:41:32 # 760480 # [E] bluray_keydb / _DebugDifference / DiscIDx2/0 - Title1 >y2< Title2 >z2<
...

Then, FindVUK suddenly stopps without any error message.

Found the bug - introduced an endless loop when parsing a keydb.cfg file with multi-line entries ...
Will be fixed in next release (hopefully ready this evening)

[nalor]

Some issues in 1.05:

- new UnitKeys are not written when there's already an entry for the DiscID in main/backup keydb



Good catch - the code to decide if it's worth to write a new entry never got updated to also consider differences in unit-keys...

Will be fixed in next release.

[ErichV]

Found the bug - introduced an endless loop when parsing a keydb.cfg file with multi-line entries ...
Will be fixed in next release (hopefully ready this evening)

:thanks:

[candela]

CloseAtTheEnd (after pressing Esc to quit Findvuk) doesn't seem to work in 1.05 (only tried with mediaplayer) . It doesn't even try so it seems to ignore the parameter. It works with 1.02

Also how can the database detect the "VUKNOTVAL" in case of busencryption , there's a comment attribute for the keys or separate comment tag?
Same question for manual title entry in case no meta title

[nalor]

Uploaded new Release 1.06 - please test and report your findings ;)

; feature: new mode 'KeyDB_ListDuplicates' to show duplicates in specified keydb.cfg
; change: HashValues are not uppercase in MetaXML
; fix: get disc size with GetDiskFreeSpaceEx instead of 'READ CAPACITY' (produces different results for original disc or iso in virtual drive)
; change: enabled to write all possible kinds of values to keydb.cfg
; fix: do not generally write _DebugDifference entries to log (only in case DEBUG loglevel is set)
; change: delete existing entries from main/backup keydb.cfg file (and add them to a 'deletedlines' file for safety)
; fix: endless loop when parsing a keydb.cfg file with multi-line entries
; fix: take UnitKeys into account when deciding if a new/changed entry should be written to keydb.cfg
; 1.06 release - 20180128

hopefully it's better than the previous release :)

[nalor]

Also how can the database detect the "VUKNOTVAL" in case of busencryption , there's a comment attribute for the keys or separate comment tag?
Same question for manual title entry in case no meta title

Only validated entries are uploaded - in case of VUKNOTVAL there's no upload.
For manual title there's an additional attribute present in the 'MetaTitle' node named Manual=1 and the specified language is the preferred one as defined in the ini file.

[nalor]

And I changed the keydb.cfg available on my temp-online-db site to the last one posted from Relight.

(but please backup your local keydb.cfg before testing the synchronization ... just to be on the safe side )

[candela]

I think there's something wrong :)


23:10:59 - Disc with ID >B2E1058AAB619B748278A03655D9E52AF4FFE44F< is already >2< times in the keydb-file
23:10:59 - -------------------------------------------------------
23:10:59 - KEYDB: Nearly identical entry already present in keydb-file (line 78585)
23:10:59 - >> Identical: TITLE, VUK, COMMENT - Different: DATE, MEDIAKEY, VOLUMEID, UNITKEYS >> write new entry in keydb-file
23:10:59 - -------------------------------------------------------
23:10:59 - KEYDB: entry for this disc already present in keydb-file (line 54947)
23:10:59 - >> but VUK is NOT identical!!
23:10:59 - >> The new VUK has been successfully validated, please report in the forum (http://forum.doom9.org/showthread.php?t=171298) that the old entry is definitely wrong!
23:10:59 - -------------------------------------------------------
23:10:59 - Final decision: write new entry
23:10:59 - There are >2< existing entries for DiscID >B2E1058AAB619B748278A03655D9E52AF4FFE44F< - remove them now
23:11:03 - Added line with VUK to file >C:\Users\\AppData\Roaming\aacs\KEYDB.cfg<


Old Lines


; Backup of deleted lines - DiscId >B2E1058AAB619B748278A03655D9E52AF4FFE44F< Date >2018.01.28 23:11:03<
0xB2E1058AAB619B748278A03655D9E52AF4FFE44F = GILDA [Gilda] | U | 1-0xD60D3E7B884C9F1B74870CE533E2E792 | I | 0x425E11297AF4A9960BD2B193B18AE61A ;
0xB2E1058AAB619B748278A03655D9E52AF4FFE44F = GILDA (Gilda) | V | 0x31767D2FA2228037F7DB30EC7C1F7A5C ; MKBv57/FindVUK 1.05


New line

0xB2E1058AAB619B748278A03655D9E52AF4FFE44F = GILDA (Gilda) | D | 2015-11-05 | V | 0x31767D2FA2228037F7DB30EC7C1F7A5C | M | 0x4C06290CC1A2C974BD9A7B1D5FF7099B | I | 0x425E11297AF4A9960BD2B193B18AE61A | U | 1-0xD60D3E7B884C9F1B74870CE533E2E792 ; MKBv57/FindVUK 1.06

Don't know why it detected a "wrong" VUK

[candela]

Also upload still fails when I try to do a second disc without closing FindVUK first (writing to keydb seems to work now)

23:22:22 - ERROR! Couldn't post the BlurayMetaXML to the OnlineDB! (http://fvonline-db.bplaced.net/fv_upload.php) >< (0)

[nalor]

; Backup of deleted lines - DiscId >B2E1058AAB619B748278A03655D9E52AF4FFE44F< Date >2018.01.28 23:11:03<
0xB2E1058AAB619B748278A03655D9E52AF4FFE44F = GILDA [Gilda] | U | 1-0xD60D3E7B884C9F1B74870CE533E2E792 | I | 0x425E11297AF4A9960BD2B193B18AE61A ;
0xB2E1058AAB619B748278A03655D9E52AF4FFE44F = GILDA (Gilda) | V | 0x31767D2FA2228037F7DB30EC7C1F7A5C ; MKBv57/FindVUK 1.05


Don't know why it detected a "wrong" VUK

Because there's no VUK present in the first entry ... so it compared an 'empty' VUK against an existing and noticed it's different ... I think I will change the message in case there's no VUK available.

[nalor]

Also upload still fails when I try to do a second disc without closing FindVUK first (writing to keydb seems to work now)

23:22:22 - ERROR! Couldn't post the BlurayMetaXML to the OnlineDB! (http://fvonline-db.bplaced.net/fv_upload.php) >< (0)

Will check tomorrow.

[nalor]

Fixed both issues in 1.07