Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
|
|
Thread Tools | Search this Thread | Display Modes |
4th July 2020, 01:56 | #521 | Link |
Registered User
Join Date: Jun 2020
Posts: 3
|
If I was to use FindVUK in conjunction with a DVDfab product, would it automatically output a properly-formatted entry for keydb.cfg? If not, I'll use the script. Concerning aacs_info and aacskeys, where can I access those? Are they bundled in libaacs.dll or are they separate programs?
|
4th July 2020, 03:34 | #522 | Link |
...?
Join Date: Nov 2005
Location: Florida
Posts: 1,420
|
aacs_info is the CLI tool that should come with libaacs, although I know many packagers probably don't bother (read: if you build libaacs, aacs_info gets built at the same time). aacskeys is a separate project, it's in the third stickied post at the top of this subforum.
The difference between what FindVUK and the script above do is that if the disc is not already in keydb.cfg, FindVUK gives you this: Code:
0x$DISCID = Gatchaman Crowds 18 BD-1 | D | 2018-08-24 | U | 1-0x$UNITKEY ; MKBv65/FindVUK 1.35 The script gives you this (in *.keydb_forinsert.txt): Code:
0x$DISCID = Gatchaman Crowds 18 BD-1 | V | 0x$VUK | M | 0x$MEDIAKEY | I | 0x$VOLUMEID ; MKBv65 Merging the two is what I was describing earlier. |
4th July 2020, 15:16 | #523 | Link |
Registered User
Join Date: Jun 2020
Posts: 3
|
Hmm...I've looked around the different forum posts and it looks like any download link for aacs_info or aacskeys have been dead for some time. I'd build libaacs and just grab aacs_info, but I can't find any build instructions. I'll look into getting a DVDfab product and using FindVUK with it to get the formatted entry for keydb.cfg.
EDIT: I downloaded the evaluation version of DVDfab PassKey for Blu-ray and FindVUK is grabbing and uploading the data without a hitch! Last edited by ZampNoxis; 4th July 2020 at 15:34. |
30th July 2020, 13:21 | #524 | Link | ||
Registered User
Join Date: Jul 2020
Posts: 1
|
Hi,
I used FindVUK a few years ago (2017) and it worked great. Trying to use it again these days and it can't seem to find DVDfab. Here's what I'm getting: Quote:
Quote:
My Windows is in French, if that changes anything. |
||
31st July 2020, 22:59 | #526 | Link | |
Registered User
Join Date: Dec 2013
Posts: 490
|
Quote:
1st it reads the entry from the inifile: section 'DVDfab' entry 'MainFile' - in case something is defined here it is always the most important source. So to solve your problem simply insert "C:\Program Files\DVDFab 11\DVDFab.exe" as 'mainfile' and it should work. In case you want to dig a little bit deeper: in case this entry is not set FindVUK tries to get this filename from the registry.
So you can check if both keys are available in your registry and if they are please tell me the exact value of the 2nd entry - maybe there's something specific on a french windows that I have to take into account. |
|
26th September 2020, 23:27 | #527 | Link |
Registered User
Join Date: Sep 2018
Posts: 2
|
Hi,
I haven't tried this since QEMU support got merged, but it still doesn't seem to be working out of the box for me as of 1.35. Same drive details as posted here: https://forum.doom9.org/showpost.php...&postcount=386 It would appear your "IsDriveQemu" function (or whatever it is that takes "QEMU" as an argument) is trying to compare "QEMU" to a null string, sees the string is null, and returns false. For now I've patched FindVUK.exe to believe that the "IsDriveQemu" function returned true, and it seems to be working fine. |
10th October 2020, 23:16 | #528 | Link |
Registered User
Join Date: May 2008
Posts: 15
|
First time using FindVUK, trying to play a disc that came out earlier this year. I'm on Windows 10, and the aacs_info program indicates my drive has MKB v76.
FindVUK couldn't locate my installation of DVDFab 12 at first, so I had to manually put the executable and log locations into FindVUK.ini. Once I did that, I was able to get as far as finding the encrypted unit key, but the program is failing on the next step. Full FindVUK log is attached, but here's (I think) the relevant part; the memory dump is over 600 MB but if there's a specific portion that would be useful I can chop out part of it. Code:
2020-10-10 14:29:30 # 57241 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >480< Content >2020.10.10-14:29:30: MD5 BBC21117B2D5D75190289BBE21C6B2B5 < 2020-10-10 14:29:30 # 57241 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >481< Content >2020.10.10-14:29:30: got vuk< 2020-10-10 14:29:30 # 57241 # [I] main / DVDfab_WatchLog_Standard(legacy) / DVDfab got VUK - create memdump now! 2020-10-10 14:29:30 # 57344 # [I] main / DumpProcessToFile(legacy) / DUMP >>> 2020-10-10 14:29:30 # 57344 # [I] main / DumpProcessToFile(legacy) / DUMP >>> ProcDump v10.0 - Sysinternals process dump utility 2020-10-10 14:29:30 # 57344 # [I] main / DumpProcessToFile(legacy) / DUMP >>> Copyright (C) 2009-2020 Mark Russinovich and Andrew Richards 2020-10-10 14:29:30 # 57344 # [I] main / DumpProcessToFile(legacy) / DUMP >>> Sysinternals - www.sysinternals.com 2020-10-10 14:29:30 # 57344 # [I] main / DumpProcessToFile(legacy) / DUMP >>> 2020-10-10 14:29:30 # 57344 # [I] main / DumpProcessToFile(legacy) / DUMP >>> [14:29:30] Dump 1 initiated: C:\Sandbox\FindVUK_1.35\dump\3DE26D88523ADD6B69B53AD42A228F8677663ADE_BRMM_10266BD1.dmp 2020-10-10 14:29:30 # 57445 # [I] main / DumpProcessToFile(legacy) / DUMP >>> [14:29:30] Dump 1 writing: Estimated dump file size is 654 MB. 2020-10-10 14:29:31 # 57950 # [I] main / DumpProcessToFile(legacy) / DUMP >>> [14:29:31] Dump 1 complete: 654 MB written in 0.6 seconds 2020-10-10 14:29:31 # 58151 # [I] main / DumpProcessToFile(legacy) / DUMP >>> [14:29:31] Dump count reached. 2020-10-10 14:29:31 # 58151 # [I] main / DumpProcessToFile(legacy) / DUMP >>> 2020-10-10 14:29:31 # 58151 # [I] main / DumpProcessToFile(legacy) / Dump successful! >1< 2020-10-10 14:29:31 # 58151 # [I] main / DumpProcessToFile(legacy) / DumpProcessToFile - Program >C:\Sandbox\FindVUK_1.35\tool\procdump64.exe< Parameter > -ma -o "DVDFab64.exe" "C:\Sandbox\FindVUK_1.35\dump\3DE26D88523ADD6B69B53AD42A228F8677663ADE_BRMM_10266BD1.dmp"< 2020-10-10 14:29:31 # 58151 # [I] main / DVDfab_DumpFile(legacy) / MemDump successfully finished! 2020-10-10 14:29:31 # 58151 # [I] main / DVDfab_WatchLog_Standard(legacy) / New Line >482< Content >2020.10.10-14:29:30: drive info: BD-RE WH16NS40 | 1.03! < 2020-10-10 14:29:31 # 58151 # [I] main / DVDfab_WatchLog_Standard(legacy) / Cancel DVDfab decryption now! 2020-10-10 14:29:31 # 58159 # [I] main / (legacy) / Get basic AACS data 2020-10-10 14:29:31 # 58160 # [I] main / FVMAIN_Mode_FindVUK_WaitForAACS(legacy) / AACS folder on disc is reachable - ValidateVUK is possible 2020-10-10 14:29:32 # 58740 # [I] main / FVMAIN_Mode_FindVUK_GetMetaInfo_AACS(legacy) / Got DiscID from disc >3DE26D88523ADD6B69B53AD42A228F8677663ADE< 2020-10-10 14:29:32 # 58741 # [I] main / FVMAIN_Mode_FindVUK_GetMetaInfo_AACS(legacy) / Got DateDiscId from disc >2020-06-15< 2020-10-10 14:29:32 # 59047 # [I] main / FVMAIN_Mode_FindVUK_GetMetaInfo_AACS(legacy) / Get encrypted UnitKeys 2020-10-10 14:29:32 # 59047 # [I] main / FVMAIN_Mode_FindVUK_GetMetaInfo_AACS(legacy) / UnitKey-Count: 1 2020-10-10 14:29:32 # 59047 # [I] main / FVMAIN_Mode_FindVUK_GetMetaInfo_AACS(legacy) / UnitKeys ENC : >1< Key >4F609DAB1C455833F2208BA472B0F0D6< 2020-10-10 14:29:32 # 59048 # [I] main / (legacy) / VolumeName >BRMM_10266BD1< 2020-10-10 14:29:32 # 59048 # [I] main / (legacy) / DiscId >3DE26D88523ADD6B69B53AD42A228F8677663ADE< (2020-06-15) 2020-10-10 14:29:32 # 59048 # [I] main / (legacy) / DiscType >BD< 2020-10-10 14:29:32 # 59048 # [I] main / (legacy) / MKB Revision >76< 2020-10-10 14:29:32 # 59048 # [I] main / (legacy) / BusEncEnabl. >0< 2020-10-10 14:29:32 # 59049 # [I] main / (legacy) / UnitKeyCount >1< 2020-10-10 14:29:32 # 59049 # [I] main / (legacy) / >>> UnitKeyENC (1) >4F609DAB1C455833F2208BA472B0F0D6< 2020-10-10 14:29:32 # 59052 # [I] main / (legacy) / Analyze dump 2020-10-10 14:29:32 # 59053 # [I] main / DVDfab_AnalyzeDump_2018(legacy) / Start to analyze '2018' MemDump now! 2020-10-10 14:29:32 # 59053 # [I] main / DVDfab_GetUnitKeysFromDump(legacy) / DVDfab_GetUnitKeysFromDump - File >C:\Sandbox\FindVUK_1.35\dump\3DE26D88523ADD6B69B53AD42A228F8677663ADE_BRMM_10266BD1.dmp< DiscID >3DE26D88523ADD6B69B53AD42A228F8677663ADE< UnitKeyCnt >1< 2020-10-10 14:29:32 # 59172 # [I] main / DVDfab_Dump_GetDraftUnitKeys(legacy) / StartAddress of last UnitKey >2184FCA< 2020-10-10 14:29:33 # 60474 # [I] main / DVDfab_GetUnitKeysFromDump(legacy) / ERROR! Couldn't find real unit keys in json from file >C:\Sandbox\FindVUK_1.35\dump\3DE26D88523ADD6B69B53AD42A228F8677663ADE_BRMM_10266BD1.dmp< 2020-10-10 14:29:33 # 60474 # [I] main / DVDfab_AnalyzeDump_2018(legacy) / Error analyzing memory dump - please report in the doom9 forum! 2020-10-10 14:29:33 # 60475 # [I] main / (legacy) / ERROR! Analyze 2018 failed! 2020-10-10 14:29:33 # 60481 # [I] main / (legacy) / CloseAtTheEnd is active, close DVDfab now 2020-10-10 14:29:33 # 60487 # [I] main / DVDfab_CloseApplication(legacy) / There are >1< DVDfab processes running 2020-10-10 14:29:44 # 71117 # [I] main / DVDfab_CloseApplication(legacy) / Friendly closing of C:\Program Files\DVDFab\DVDFab 12\DVDFab64.exe< didn't succeed - kill it unfriendly now |
11th October 2020, 14:01 | #529 | Link | |
Registered User
Join Date: Jun 2005
Posts: 259
|
Quote:
|
|
13th October 2020, 02:33 | #530 | Link |
Registered User
Join Date: May 2008
Posts: 15
|
I'll give it a shot, but according to the changelog in the first post of this thread, support for DVDFab 12 was added in FindVUK 1.30; I'm using v1.35. (Though the log file warns that DVDFab 12.0 is "untested," which seems a bit contradictory to me...)
|
13th October 2020, 05:41 | #531 | Link | |
Registered User
Join Date: Dec 2013
Posts: 490
|
Quote:
Will release a new findvuk today to handle this. But when specifying both mainfile and logfile correctly in the ini file, it's already working with the current findvuk for me. Gesendet von meinem H8324 mit Tapatalk |
|
13th October 2020, 12:08 | #533 | Link | |
Registered User
Join Date: Dec 2013
Posts: 490
|
Quote:
Basically it's a 2 step process that is executed here:
In case it fails please first check if it's working the next time - and else upload the dump somewhere and send me the link. |
|
15th October 2020, 03:30 | #534 | Link |
Registered User
Join Date: May 2008
Posts: 15
|
Updated to FindVUK 1.37 (and DVDFab 12.0.0.1) and it's working like a charm. Thanks!
Also, here's my drive info for inclusion in the database: Code:
2020.10.13 08:23:51 - Please post the following information into the doom9 forum thread: http://forum.doom9.org/showthread.php?t=172914 + VENDOR # PRODUCT-IDENTIF. # REV. # FIRMWARE CR. # INTERFACE # DRIVETYPE # BusEncryptionCapable # BindingNonceGeneration # VENDOR SPECIFIC # FEATURE DESCRIPTOR # COMMENT | HL-DT-ST | BD-RE WH16NS40 | 1.03 | 211711211653 | Serial ATAPI | BLURAY/DVD/CD-WRITER | 1 | 1 | NM00600SIK9CH158462 | 01 0D 09 04 17 01 02 01 | |
16th October 2020, 07:10 | #535 | Link |
Registered User
Join Date: Jun 2020
Posts: 9
|
Hey nalor, cool to see FindVUK get another update! However, I'm wondering about something. Since updating, I get these strange excel files in the "accs" folder in APPDATA. They have weird names like "KEYDB_Diff_BRKDB_20201015_051659" and "KEYDB_Diff1_20201015_051659". I assume it's some sort of log or check that the program does since it has things like "TITLE" and "MEDIAKEY" as column names, but I just wanted to ask about them since I don't really know what they are and if I should keep them or if I can simply delete them if I want (or if there is an option to make the program delete them automatically after it is done with them).
Also, since I'm making this post anyway, I noticed that the FindVUK.ini file has the version set to 1.35 ("IniVersion = 1.35" in the file itself). Is that normal or do I need to do some sort of full reinstall by getting rid of certain files or the like? Probably not an issue I would imagine, but just wanted to mention it just in case it's related in some way. PS. If you need me to upload the files I can certainly do that with TinyUpload, just didn't know if that was necessary in this case. |
16th October 2020, 11:26 | #536 | Link |
Registered User
Join Date: Dec 2013
Posts: 490
|
Those files can be deleted, I missed to disable the creation before creating the release.
They include debug information about the synchronisation process. In the next release it wil be possible to enable them with a ini parameter. The version in the ini file depends on the latest release with changes in the ini file, so in your case I haven't made changes since release 1.35 But it's a good idea to change this behaviour Gesendet von meinem H8324 mit Tapatalk |
9th November 2020, 02:37 | #539 | Link |
Registered User
Join Date: Oct 2020
Posts: 10
|
The tool asked me to post this:
++++++++++ 17:35:06 - --- PART 2 --- VALIDATE VUK/UNITKEYS --- ------------------------------------------------------------------------------- 17:35:06 - Drive is detected as 'REAL BLURAY' drive 17:35:06 - Drive is NOT in the KnownDrivesList! 17:35:06 - Please post the following information in the Doom9 forum to create a comprehensive list of drives: 17:35:06 - (you'll find this information + additional details also in the file >C:\Unzipped\FindVUK_1.38\PleasePostInDoom9Forum.txt< 17:35:06 - + VENDOR # PRODUCT-IDENTIF. # REV. # FIRMWARE CR. # INTERFACE # DRIVETYPE # BusEncryptionCapable # BindingNonceGeneration # VENDOR SPECIFIC # FEATURE DESCRIPTOR # COMMENT 17:35:06 - | ASUS | BW-16D1HT | 3.03 | 211801191558 | Serial ATAPI | BLURAY/DVD/CD-WRITER | 1 | 1 | W000000KEII6190829 | 01 0D 09 04 1F 01 02 01 | 17:35:07 - Added this entry to the list of known drives so the request to post the details of this drive will not be shown again |
9th November 2020, 02:39 | #540 | Link |
Registered User
Join Date: Oct 2020
Posts: 10
|
-------------------------------------------------------------------------------
17:38:08 - Validation successful! UnitKeys are valid!! ------------------------------------------------------------------------------- 17:38:08 - ------------------------------------------------------- 17:38:08 - MetaTitle : Metallica- SM2 17:38:08 - VolumeName : Metallica - SM2 17:38:08 - DiscID : BA4590CA75E050E4760DBA62404EBCB9A6749235 17:38:08 - DateDiscID : 2020-02-10 17:38:08 - DiscType : BD 17:38:08 - VUK : 17:38:08 - MEDIAKEY : 17:38:08 - VOLUMEID : 17:38:08 - >>> UnitKeyDEC (1) >0A34A4EC251DA52D7273B2D8B398ABBF< (Valid) 17:38:08 - MKBrev : 72 17:38:08 - BusEncrEn : 0 17:38:08 - AACS : 1 17:38:08 - BD+ : 0 17:38:08 - ------------------------------------------------------- ------------------------------------------------------------------------------- 17:38:08 - --- Write entry in main-keydb file --- ------------------------------------------------------------------------------- 17:38:08 - Keys in Keyfile: 108887 keys - KeyFile: C:\Users\nuram\AppData\Roaming\aacs\KEYDB.cfg 17:38:08 - KEYDB: no entry found for discid >BA4590CA75E050E4760DBA62404EBCB9A6749235< ==>> write new entry in keydb-file 17:38:09 - Added line with VUK/UnitKeys to file >C:\Users\nuram\AppData\Roaming\aacs\KEYDB.cfg< 17:38:09 - ------------------------------------------------------- 17:38:09 - --- Write entry in backup-keydb file --- 17:38:09 - ------------------------------------------------------- 17:38:09 - KEYDB: file >C:\Unzipped\FindVUK_1.38\VUKbackup\KEYDB.cfg< does not exist ==>> write new entry in keydb-file 17:38:09 - Added line with VUK/UnitKeys to backup-file >C:\Unzipped\FindVUK_1.38\VUKbackup\KEYDB.cfg< 17:38:09 - ------------------------------------------------------- 17:38:09 - --- Upload MetaXML to OnlineDB file --- 17:38:09 - ------------------------------------------------------- Establishing connection Establishing connection HTTP-POST success 17:38:10 - Successfully posted to the OnlineDB! > Preconditions fulfilled - process upload now Detected BlurayMetaXML - DiscId >BA4590CA75E050E4760DBA62404EBCB9A6749235< Upload written to database! Upload successfully processed! < 17:38:10 - Successful upload to OnlineDB 17:38:10 - Hash file not available - nothing to update 17:38:10 - Eject the disc now from drive >D:\< |
Thread Tools | Search this Thread |
Display Modes | |
|
|