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

[nalor]

A few words of introduction:

As we all know there's no chance to free the Bluray format as it happened with the DVD.
There are no working processing keys available anymore and even if it would, they would get revoked within a short period of time.

The only thing that is forever (at least for AACS) is the VUK (Volume Unique Key).

About february 2014 I got my first raspberry pi, connected a usb-bluray drive and tried to play a few blurays but simply got disappointed: apart from the problem that the first pi was simply not fast enough to handle the usb-bluray and the decoding I also ran into the problem that the necessary library 'libaacs' needs a VUK for each Bluray to decode it properly - but those keys are only available for older Blurays as the newer ones cannot be decrypted any longer because of the missing processing keys....
Usually 'MakeMKV' is a quite good replacement for libaacs under linux - but at the time where the FindVUK started it has not been available for ARM devices (I think now it is: MakeMKV on Raspberry PI (ARM) (https://forum.makemkv.com/forum/viewtopic.php?style=3&p=105912#p105912)).

In August 2015 I stumbled across this post here http://forum.kodi.tv/showthread.php?tid=230493 and started thinking about the VUK problem again.

I already asked the MakeMKV developer in the past to output the VUK so it can be used on arm devices - but he replied that it's too complicated to get the vuk from his tool.

But than I got hands on another tool called 'DVDfab Passkey' and noticed an interesting line in it's logfile: 0m 58.68s: got vuk
So I posted a feature request in their forum to write the VUK into the logfile - but until now I've got no reply to it.

But I discovered another way to get the VUK from Passkey: create a memory dump after decrypting and read it from the dump :)

How you can 'find the VUK' manually (without FindVUK):

Basically the steps are quite easy:

start a DVDfab application (Passkey, MediaPlayer or DVDfab9)
insert a bluray
in case you're using MediaPlayer start the playback
in case of Passkey or DVDfab9: wait until the analyzing finishes
create a memory dump with e.g. the windows task manager
open the dump with a hex editor and search for the discid (it can be found in the logfile of passkey)
and a few bytes later you'll find the vuk in the file (for newer releases only the unit keys are present in the dump)


What FindVUK does:
Originally FindVUK was only a proof-of-concept to get the VUK from a dvdfab memory dump, but it evolved and also received a few more features:

Main feature: monitor the logfile of different DVDfab applications, dump the memory when the relevant data is available, extract vuk or unit keys from the dump and validate the data against the disc in the drive. finally the result is uploaded to a central bluray-database
Synchronize mode: synchronizes the 'keydb.cfg' file with the online database
AACSkeys mode: calls the well known aacskeys utility to read MediaKey, VolumeId and VUK, validates the data against the current disc and finally the result is uploaded to a central bluray-database
ValidateVUK mode: simple test to check if a VUK matches the disc in a drive - no upload to the database is performed
ValidateDisc mode: monitors a defined drive and checks for each inserted disc if there's a matching entry in the keydb.cfg file and if this entry is valid and finally the result is uploaded to a central bluray-database
ShowDriveDetails mode: just displays technical details of either all drives or a specific drive
GetMetaInfoFromDisc mode: reads meta-data from the disc in the specified drive and uploads it to the central bluray-database
KeyDB_ListDuplicates mode: checks the keydb-file for duplicate entries


The KEYDB.cfg file is used by the libaacs library (that can be used to play blurays for example in VLC).

FindVUK is windows only - in case you're a linux user take a look at VukExtract (https://forum.doom9.org/showthread.php?t=174404) from @m4tthi4s

Getting started:


Select your DVDfab tool of choice (personally I bought a DVDfab Passkey license), download and install it http://www.dvdfab.cn

Passkey: last supported version is 9.4.5.2 (newer versions are not compatible any longer)
DVDfab: still working even in DVDfab 13.x (tested on 2026.03.21)
PlayerFab: still working in PlayerFab 7.0.5.5 (tested on 2026.03.24)

Download and extract FindVUK into a new directory
Execute FindVUK (during the first start it will download the dump-tool from the sysinternals website and start it so you can accept the license)

Alternatively download 'procdump.exe' (x86 version) manually and copy it into a subdirectory called 'tool'

Insert a Blu-ray into your drive
You're using Passkey or DVDfabXX: it automatically start to decrypt the disc - FindVUK will watch the logfile, create a memory dump when Passkey/DVDfabXX got the VUK/UnitKeys, stop the Passkey/DVDfabXX decrypting process and analyze the memory dump to get the VUK/UnitKeys. Finally it will validate it against the disc and in case it's valid add it to the end of the local KEYDB.cfg
You're using MediaPlayer: Please start the playback of the disc manually - FindVUK will watch the logfile, create a memory dump when Mediaplayer got the VUK/UnitKeys, close MediaPlayer and analyze the memory dump to get the VUK/UnitKeys. Finally it will validate it against the disc and in case it's valid add it to the end of the local KEYDB.cfg (and restart's MediaPlayer for the next analysis cycle)
Repeat the previous 2 steps until you got the VUK for all your Blurays
At the end of each cycle FindVUK uploads the complete data-set to the online-database


Whenever DVDfab releases a new version of either DVDfab, MediaPlayer or Passkey I'll test if FindVuk is still compatible and include it into an internal 'known to be good' list and will release a new version that includes this result. But even in case I'm not fast enough - FindVUK will simply report that the used DVDfab application is untested.

I hope the company behind the application don't close this way of retrieving the VUK or at least the unit keys.

In case you have problems with the tool please post your experience here and I'll try to help as good as I can :)

History of the tool:

(had to clean the details of the first releases because I hit the size limit of this post ;)
-> the full changelog of all releases is included in the zip-file of the download

20150812 .. 0.51 - initial release
(...)

20211113 .. Download FindVUK 1.54 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.54.zip)

CHANGE: upload of devicekeys, processingkeys and hostcertificates disabled by default and can be enabled with ini parameter


20220501 .. Download FindVUK 1.55 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.55.zip)

FIX: \ and / in Volumenames do not cause a problem any longer


20220515 .. Download FindVUK 1.57 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.57.zip)

FIX: 2nd try - \ and / in Volumenames do not cause a problem any longer
FIX: BD+ not detected in aacskeys mode
FIX: copy protection check broken in 1.56


20230122 .. Download FindVUK 1.58 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.58.zip)

FIX: add support for Passkey 9.4.5.1
CHANGE: add support for MS Windows 10 virtual drive
FIX: repair support for virtual drives
CHANGE: report success if all unit-keys are validated (should fix handling of disc >WINX-IL MISTERO DEGLI ABISSI<)


20230203 .. Download FindVUK 1.59 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.59.zip)

FEATURE: add support for Passkey 9.4.5.2



20230425 .. Download FindVUK 1.63 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.63.zip)

CHANGE: better logoutput in case online-upload is disabled
FEATURE: support to get ReadDataKey (RDK) from Passkey Dump (in case BusEncryption is active)
FEATURE: validation of Unitkeys is using RDK (in case of BusEncryption)
CHANGE: speedup during validation - first collect all M2TS files and check if it's encrypted only if required (usually not all files are necessary to validate all unit keys)
BAD NEWS: Passkey 9.4.5.3 does not provide the UnitKeys any longer in the memory dump - so it's flagged as "not working" :(
FEATURE: introduce support for FabPlayer 7 (tested with 7.0.3.6 and it's working)
FIX: problem with Unitkey Validation


20230626 .. Download FindVUK 1.64 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.64.zip)

FIX: do not write an error if a local processing_key, device_key or host_certificate is not available
FIX: support DVDfab up to 12.1.0.9


20230919 .. Download FindVUK 1.66 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.66.zip)

FIX/IMPROVE: support DVDfab up to 12.1.1.5


20230920 .. Download FindVUK 1.67 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.67.zip)

FIX: correctly update hash file after keydb sync


20231208 .. Download FindVUK 1.72 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.72.zip)

CHANGE: treat unitkeys with lots of 0es with lower priority as local entries so those get uploaded to fvonlinedb during sync
FEATURE: added basic AACS2 support
FEATURE: added MakeMKV Libredrive support to disable BusEncryption for validation of UHD discs (see https://forum.makemkv.com/forum/viewtopic.php?t=19029 )
FEATURE: support for DVDfab 13 (tested with 13.0.0.7)
FIX: assume logfile for DVDfab 13 is always enabled
FEATURE: new INI switch "MakeMKV_Libredrive_Enabled" to enable Libredrive support if desired/required - but it's disabled by default


20240504 .. Download FindVUK 1.74 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.74.zip)

FEATURE: new mode "validateDisc" that monitors a drive, validates each disc that get inserted and upload the result
FEATURE: option to integrate external tools to either disable BusEncryption and/or provide a RDK file


20240508 .. Download FindVUK 1.75 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.75.zip)

FIX: correctly calculate DriveId for AACS2 drives
CHANGE: use internal UDF parser to get creation date of "\AACS\Unit_Key_RO.inf" for DateDiscId (fixes problem with Linux/Wine to return the modification timestamp as creation timestamp)
CHANGE: use new procedure BRAACS_getVolumeName to read volumename, includes a fallback to read directly from udf filesystem in case operating system returns an empty string
CHANGE: prevent to upload meta-entries with empty: discid, datediscid, volumename, disctype


20240804 .. Download FindVUK 1.77 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.77.zip)

FIX: correctly read udf volumename (possible additional weird character at the end)
FIX: in case first unitkey-location is not the correct one keep searching until the end of the file


20240904 .. Download FindVUK 1.79 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.79.zip)

FIX: do not write error for backup/restore of window position when used with Windows Terminal (simply do nothing instead as this is not yet supported)
FEATURE: support DVDfab 13.0.2.5/13.0.2.6



20240913 .. Download FindVUK 1.80 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.80.zip)

FIX: always read volumename directly from UDF filesystem, never rely on windows internal call (hopefully fixes problem in linux/wine environment)


20250318 .. Download FindVUK 1.81 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.81.zip)

FEATURE: extra protection to prevent validated disc uploads without a valid unitkey
FIX: correctly flag unitkeys, which are in combination with busencryption detected as invalid, as invalid and log that possibly the read data key is wrong


20250329 .. Download FindVUK 1.82 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.82.zip)

FIX: do not eject twice during "validate disc"
FIX: correctly take "ExitAfterProcessing" into account in "validate disc" mode - note: in case EjectDisc=0 and ExitAfterProcessing=0 - the disc is still ejected to prevent an endless validation loop
CHANGE: log selected AppMode into logfile
FIX: correctly abort disc-validation in case no entry for the disc is available in the keydb.cfg file
FIX: disc-eject fixed: correctly lock and dismount, in case lock is not possible, it's ejected without locking first


20260328 .. Download FindVUK 1.83 (http://fvonline-db.bplaced.net/findvuk/FindVUK_1.83.zip)

FIX: validating a disc correctly removes the '(NOTVALIDATED)' from keydb.cfg entry comment
FEATURE: validating a disc tries to validate in all combinations: volumeid+mediakey, vuk or only the unitkeys
FEATURE: keydb ordering and comment pattern identical in online file and the entries created by FindVUK
CHANGE: volumesize is now calculated from disc-details instead of calling MS function "GetDiskFreeSpaceEx"
FIX: hash-file has been updated although it was already out of sync before. Is fixed now, but needs a fresh full sync from online db to ensure it's really in sync again :(
FIX: do not detect RDK as (incorrect) unitkey when searching for unitkeys in dump
CHANGE: do not ask any longer to post new drives in forum
FIX: DVDfab keeps UnitKeys of previous discs in memory and so they are still present in dumps of following discs, so found unitkeys are stored in an internal list in order to know if a detected one is "new" or just an old entry
FIX: when searching for multiple unitkeys do not report an error if only 1 is found, instead carry on with search until the end of the file

[nalor]

Released 0.54 - details see first post (not that hard to find ;)

[mpfour]

Source?

Also, a version with options to disable anything that uses a network connection in your program would be good.

[candela]

Holy crap. It works! Amazing find. :thanks:

Unfortunately DVDFabPasskey doesn't appear to work without internet connection so they can, and probably will, make the current versions stop working and block your program :( But let's hope and get as many keys as possible in the meantime

[nalor]

@mpfour:

It's written in Purebasic and at the moment I don't want to release the source - but maybe this will change in the future...

And basically there's nothing in the software that uses an online connection with one small exception - in case the 'procdump.exe' in the 'tool' subdirectory is not available the tool tries to download it automatically from the location that is specified in the ini file with 'ProcDumpUrl'.
Until now I never thought someone could have problems with this download - but I've changed the error message in case the URL is empty to something more readable :)

So in case you want to run it right from the start without any network activities simply create the FindVUK.ini file in the 'config' subdirectory manually and delete the procdumpurl from the ini file - for example this here should do the trick:

[Passkey]
LogFolder = %userprofile%\Documents\DVDFab Passkey\Log
MainFile =
[FindVUK]
KEYDB_Path = %userprofile%\AppData\Roaming\aacs
ProcDumpUrl =
CustomOffset_Folder2DiscId =
CustomOffset_DiscId2Vuk =

So Release 0.55 only includes the change of the error message in case of an empty download url:

Old Message:
ProcDump is not available right now at >C:\FindVUK\tool\procdump.exe< - download a fresh copy now from ><
ERROR! receiving ><
ERROR! getting procdump - end now

New Message:

Error - ProcDump is not available here >C:\FindVUK\tool\procdump.exe< and no download URL is specified!
Please download it manually from the SysInternals website

[nalor]

@candela:

Thanks for your positive post! :)

I also thought a lot if DVDfab will change their software to prevent that the VUK can be extracted from a memory dump - but personally I think that the VUK is only usefull for playback of blurays and although it can also be used to decrypt blurays I'm not aware of a convenient tool to do this.

So finally I don't think that somebody stops buying software from them because they don't sell bluray playback software :)

On the other hand it might be a reason to buy software from them to get the possibility to detect the VUK for certain blurays that couldn't be watched on a linux device otherwise...

But as I can't change it anyway I'm with you: get as many keys as possible as long as it works :D

[nalor]

Uploaded latest version 0.55 also to file-upload.net and added the link in the first post.

[nalor]

Posted 0.56 a couple of days ago and added a file-upload.net link now (because it hasn't been approved by an administrator yet).

[nalor]

update: 0.57 with 2 bugfixes available in first post

[nalor]

Just a small info: DVDfab has the next promotion running and is giving away free lifetime licenses for DVDfab MediaPlayer pro (and in the next version of FindVUK you can also use MediaPlayer pro to find the vuk :)

http://de.dvdfab.cn/promotion.htm

And personally I find it more convenient to work with MediaPlayer than to work with Passkey :)

[nalor]

Okay - just finished my last internal tests for the next small update to FindVUK and attached version 0.61 in the first post :)

The biggest change is the additional support for 2 more products from DVDfab:


MediaPlayer Pro
DVDfab9


As already mentioned DVDfab has a promotion running to give away MediaPlayer pro lifetime licenses for free and when I installed this player I checked the memory dump and noticed that the same method to find the vuk can also be used for this software.
Finally I've tried it also for DVDfab9 and as expected it's also possible to get the VUK from it's memory dump :)
And as far as I can see the VUK can also be found with the trial version of DVDfab9 and as long as the 'main' features of DVDfab aren't used the 'real' trial period never starts and subsequently it will never expire ;)

As FindVUK has still no interface it's settings are still controlled with the ini-file in the 'config' subdirectory - the ini-file got a few new parameters that I'd like to explain in short:

Section 'MediaPlayer' (and Section 'Passkey' - but this one has been in the ini-file since the first release)

LogFolder holds the default logdirectory for this applications - basically FindVUK reads the registry to get the currently configured logfolder so this key is only used in case the automatic detection fails (for example in case the registry key that is read at the moment get removed in an upcoming release or something like this...)
MainFile holds the path to the main exe file of the application - in case the path is empty it is also directly retrieved from the registry, so at the moment there's no need to specify it manually


Section 'DVDfab' (basically identical to the sections 'Passkey' and 'MediaPlayer' with one exception):

LogFile holds the complete logpath including the filename at the end - this is possible because for DVDfab also the filename can be specified in the settings, for MediaPlayer and Passkey only the folder can be set.


Section 'FindVUK'

PreferredApplication - this is basically the most important new parameter, as FindVUK now supports 3 different applications this is the way to decide which one should be used in case more than 1 of the supported applications is installed on the computer. 1=Passkey, 2=MediaPlayer, 3=DVDfab
IniVersion - makes no sense to change it manually, I use it to detect the current version of the ini file and automatically add new (or remove old) parameters


Personally I prefer using MediaPlayer and DVDfab9 against Passkey because for both new applications it's always possible to get access to the encrypted disc and this allows to validate the found VUK without the need to disable or exit an application (as it happens quite frequently with Passkey).

When using MediaPlayer you need to start the playback of the disc in MediaPlayer and as soon as the VUK has been found FindVUK will stop the playback and exit the MediaPlayer (but of course also start it again for the next disc) - this is necessary because MediaPlayer caches the result of it's internal analysis and so it wouldn't be possible to insert the same disc 2 times in a row (something that I'm doing quite often during my own tests ;) ).

DVDfab9 doesn't cache any results - so it's not closed in the middle, simply insert one disc after the other without the need for any manual interaction :)

In case you run into troubles using FindVUK don't hesitate to post a reply here - and in case it's working perfectly for you I also appreciate positive feedback :D

[candela]

I only have Passkey and Media Player installed and then FindVUK refuses to start unless I put a valid (fake) DVDFab path in the ini

Log file says:
DVDFab "Warning! DVDfab MainApp is not valid! >< - please check if it is installed properly!"

[nalor]

Thanks for the bug report! :thanks: - already corrected the error... stupid mistake, don't know why I've treated the 'Warning' messages as errors...

Please try 0.62 now - it should work as expected (only exit in case not a single supported application can be found)

[candela]

Thanks 0.62 works. The Media Player is indeed a much better option than Passkey which always locks my drive and often crashes when I try to close it. No such problems with Media Player so far

[shadowofdarkness]

I'm trying to get this to run but it keeps giving a error and I don't know what to do. I only have temporary access to a Windows machine (I only run Linux) so I need to figure this out fast.
I already added added about 140 vuk's to the KeyDB that I could from a Linux machine now I want to get the rest of my v31+ discs done will I can so they well play under Linux after a KeyDB update.

Output

-----------------------------------------------------------
2013.11.20 06:32:18 - ------------ FindVUK 0.62 ------------
-----------------------------------------------------------
2013.11.20 06:32:18 - SettingsFile: >C:\Users\username\Desktop\FindVUK\con
fig\FindVUK.ini<

2013.11.20 06:32:18 - Passkey is preferred and available!
2013.11.20 06:32:18 - Passkey-MainFile:>C:\Program Files\DVDFab Passkey\DVDFabPa
sskey.exe
2013.11.20 06:32:18 - Passkey-LogFile: >C:\Users\username\Documents\DVDFab
Passkey\Log\passkey_internal.log
2013.11.20 06:32:18 - KEYDB-Path: >C:\Users\username\AppData\Roaming\
aacs

2013.11.20 06:32:18 - ProcDumpFile: >C:\Users\username\Desktop\FindVUK\
tool\procdump.exe

###############################################################################
--- PART 1 --- GET VUK ---
-------------------------------------------------------------------------------
2013.11.20 06:32:18 - Please make sure Passkey is enabled!
-------------------------------------------------------------------------------
2013.11.20 06:32:18 - Tested Passkey Version >8.2.4.8< found
2013.11.20 06:32:18 - >>> everything should work as expected!
2013.11.20 06:32:18 - Offset Folder2DiscId >0x114< - DiscId2Vuk >0x5F<
2013.11.20 06:32:31 - Drive opened
2013.11.20 06:32:34 - DiscType detected >Blu-ray BDMV<
2013.11.20 06:32:34 - Volume Label detected >GAME_OF_THRONES_S2_EPISODE_ONE▼<
2013.11.20 06:32:34 - DriveLetter detected >D<
2013.11.20 06:32:34 - Detected CopyProtections AACS >1< BD+ >0<
2013.11.20 06:32:35 - DiscID found >AB6DAF1F77EEB06782525D440B84CF4F52D96452<
2013.11.20 06:32:36 - Passkey got VUK! Cancel decryption and create MemDump now!

2013.11.20 06:32:37 - Dump successful! >0<
2013.11.20 06:32:37 - MemDump successfully finished!
2013.11.20 06:32:37 - Start to analyze MemDump now!
2013.11.20 06:32:37 - Error! DVDfab_GetVukFromDump - Couldn't find Vid in File!!
!
2013.11.20 06:32:37 - Error during analyzing memory dump - please report in the
doom9 forum!
2013.11.20 06:32:37 - ERROR! while analyzing the memory dump! Exit application!
Waiting 3 secs before quit...

Edit: It turns out it is only that one disc when I tried others they worked. I just have to figure out that one now.
Although I found 10 discs in the end that FindVUK said were invalid but when I manually added them from the terminal output into the keydb on my Linux system (no other decryption software running just libaacs) and manually tested they worked great. They were Game of Thrones seasons 3 and 4 plus the 3D disc for Jurassic Park

Another strange thing when I went to add those last ones with the updater it only added 9 but I had 10 and none of them worked before I added the vuks so they didn't exist beforehand in the DB

[nalor]

Hi! So as far as I can see you encountered 3 strange things ;)

1) FindVUK cannot find the necessary data in the memory dump for the >GAME_OF_THRONES_S2_EPISODE_ONE▼< bluray.
>> in this case the memory dump should still be available in the dump subdirectory of the findvuk folder - it would be great if you could upload it somewhere and send me the location as pm so I can download it and check what is going wrong in this case.
You can check yourself with a hex editor if you can find the DiscId >AB6DAF1F77EEB06782525D440B84CF4F52D96452< in the memory dump.

2) FindVUK reported the found VUK to be invalid but it still works? Please post the logfile from such a disc - in case there's something wrong in my validation routine I'd like to correct it as soon as possible :)

3) The updater only updates 9 of 10 keys - well, please report this in the thread of the updater as honestly I have no idea why this is happening...

[shadowofdarkness]

Hi! So as far as I can see you encountered 3 strange things ;)

1) FindVUK cannot find the necessary data in the memory dump for the >GAME_OF_THRONES_S2_EPISODE_ONE▼< bluray.
>> in this case the memory dump should still be available in the dump subdirectory of the findvuk folder - it would be great if you could upload it somewhere and send me the location as pm so I can download it and check what is going wrong in this case.
You can check yourself with a hex editor if you can find the DiscId >AB6DAF1F77EEB06782525D440B84CF4F52D96452< in the memory dump.

2) FindVUK reported the found VUK to be invalid but it still works? Please post the logfile from such a disc - in case there's something wrong in my validation routine I'd like to correct it as soon as possible :)

3) The updater only updates 9 of 10 keys - well, please report this in the thread of the updater as honestly I have no idea why this is happening...

1) It turns out the problem with the Game of Thrones disc is that it can't create the dump file which can be seen by it having some strange character at the end of the volume label.

To make it worse for you to figure out I tried putting the log on pastebin but that character was deleted even opening the txt file in Notepad on Windows didn't show it. The only way I even saw it was when I opened the log file on my Linux machine.

I have attached the original txt file in case you also run Linux to see it and a screenshot of it open in vi incase you don't. I didn't even have to highlight the problems since it seems highlighted on its own.

2) The log is also doing the Jurassic Park 3D discs which gives a false invalid. But I know works since I have propagated it manually to my Linux laptop and Raspberry Pi which both started playing the disc fine afterwards.

3) I'll definitely find the updater thread because I may also have others that didn't upload but I thought it was coincidence that someone else added them because I got a updated db as I was doing the upload that time. But maybe not if it also added less this time when no other update happened.

[nalor]

Ahh! You're right - this strange character will be the problem! I'm only wondering why procdump.exe doesn't return an error when it fails because of the filename...

I'll remove all strange characters in future from the filename - I think this will solve the problem :)

Give me a few minutes - I'll upload the next release soon!

Unfortunately I cannot download your logfile because it still needs approval... maybe you can simply upload it to file-upload.net or another easy to use filehoster and paste the link here?

[shadowofdarkness]

Here is the log also I noticed the character looks different when I open it in gedit on my Linux system so it's like it just shows something as a place holder and not a specific character.

http://s000.tinyupload.com/index.php?file_id=87366803134481590036

[nalor]

Thanks for the logfile! This really helps! I think I already know the problem with VUK-invalid message.. it's again a stupid error :(
I'm only wondering why I've never run into this problem before....

I'll fix it now and as soon as I've finished this task I'll upload the next release :)

[nalor]

Released FindVUK 0.65 - it should fix all problems reported by shadowofdarkness and has a few additional features :)

After the last keydb update of Starbuck2010 I noticed there are a few discs with volumename 'BDROM' - as this isn't that meaningful I implemented a new feature that reads the movie-title from the meta-files on the disc.
The metafiles can be available for different languages - and so I've introduced 2 new ini parameters for this feature:

Section 'BlurayMeta'

PreferredLanguages - this allows to specify an order of preferred languages, e.g. 'deu,fra,ita,spa,eng' means that it should try to read at first the german title, in case it's not available read the french title, next the italian title, ... in case this parameter is empty it always tries to read the english title and when this isn't available it simply takes the first meta file available. so usually you only have to specify your own language (in case it's different from english) and not a complete list :)
AlwaysAddMetaTitleToVolumename - usually the meta-title is only added to the volumename in the keydb-file when the volumename is 'BDROM' - when you set this parameter to 1 it is always added


(Update 201510111: I've checked FindVUK 0.80 with my complete bluray-library and there are the names of all languages that I've found on my discs:

ces = czech
deu = german (also found 'gem' on IceAge3 that is also german - taking care of it internally in FindVUK)
eng = english
fra = french
hun = hungarian
ita = italian
jpn = japanese
nld = dutch
pol = polish
rus = russian
spa = spanish
tur = turkish

So basically I think the ISO 639-2/T 3 character codes are used: Wikipedia-List_of_ISO_639-1_codes (https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes)
)

When the meta-title is added to the volumename it is surrounded by parenthesis - e.g. BDROM (This is the Meta-Title)
In case the volumename is BDROM but no meta-files are available on the disc (as it is for example on the Resident Evil bluray) FindVUK asks you to input the Movie Title manually - in this case it is added to the volumename and surrounded by square brackets - e.g. BDROM [Resident Evil]

The next thing I noticed when studying the post from Starbuck2010 is that the comments field in the keyfile is limited to 40 characters - so I shortened everything that FindVUK writes in the comment section to stay within this limit:

changed all ' - ' separator to '/'
changed 'BusEncrEn' to 'BEE'
changed 'MKBrev xx' to 'MKBvxx'
changed 'VUKNOTVALIDATED!!' warning to 'VUKNOTVAL!'

>> at the moment even in the worst case it should not exceed 38 characters :) (e.g. MKBv99/BD+/BEE/VUKNOTVAL!/FindVUK 0.65)

And a few bugfixes - the biggest is a correction to a stupid mistake - although I already had a loop to try all available unit-keys I stopped the loop when the first one didn't match... :(

@shadowofdarkness: please report if it really corrects all your problems - thanks :)

[shadowofdarkness]

v0.65 fixed both problems. Thanks.

[Neph]

I'm currently trying to get the VUK of a few german blu-rays with the DVDFab Media Player and version 0.65 of FindVUK.

For "Maze Runner": I opened FindVUK, agreed to the Eula, it then opened the media player on its own and I started the playback but when I then started FindVUK again, it only gave me the following error message:
Error! Couldn't open the DVDfab logfile......
ERROR, couldn't follow the logfile properly

I then created the dumpfile manually, opened it with TextPad and there's really some kind of VUK after the disc ID (disc ID, a few random symbols, path of the Temp folder, then the kinda VUK twice) but it's too long compared to the VUKs in the KEYDB.cfg file.
I already tested it with a few other blu-rays (Mama, RED 2, Paranormal Activity: The Marked Ones, Resident Evil: Retribution, Iron Man 3) but it always gave me the same error message in your program and it didn't even put any kind of VUK into the dump file. VLC still can't read the BRs and acts like it's simply missing the VUK. The DVDFab Media Player can play them just fine and it always got the VUK according to the logfile but, like I said, I can't find the actual VUK to add those blu-rays to the database.

Any recommendations, what I could do to fix it and/or find the real VUK?

[nalor]

Hi!
When you start FindVUK - does it print the correct filename for the Mediaplayer-Logfile?

In my case I get this Information displayed directly after the start:

-----------------------------------------------------------
2015.09.27 18:27:34 - ----------- FindVUK yyy -----------
-----------------------------------------------------------
2015.09.27 18:27:34 - SettingsFile: >C:\FindVUK\config\FindVUK.ini<

2015.09.27 18:27:34 - MediaPlayer is preferred and available!
2015.09.27 18:27:34 - MediaPlayer-MainFile: >C:\Program Files (x86)\DVDFab Media Player 2\FabPlayer.exe<
2015.09.27 18:27:34 - MediaPlayer-LogFile: >C:\Users\xxx\Documents\DVDFab Media Player\\win_player.log<
2015.09.27 18:27:34 - KEYDB-Path: >C:\Users\xxx\AppData\Roaming\aacs<
2015.09.27 18:27:34 - ProcDumpFile: >C:\FindVUK\tool\procdump.exe<

So in my case it detected 'C:\Users\xxx\Documents\DVDFab Media Player\\win_player.log' as the logfile of MediaPlayer - can you check if the logfile that is shown in your case is the correct one? Does it really exist?
(I just noticed the double \\ in the path, this is fixed in the next version, but I'm not aware of any problems related to this issue)

And another question - as far as I know MediaPlayer isn't working at the moment due to the changes of the server software from dvdfab: DVDfab Forum: Media Player Pro refuses to open blu-rays (http://forum.dvdfab.cn/showthread.php?t=27838)

Can you still watch Blurays with MediaPlayer on your computer?

[Neph]

Here's what it shows me with R.E.D. 2:
2015-09-27 20:12:23 # 23097840 # ----------- FindVUK 0.65 -----------
2015-09-27 20:12:23 # 23097842 # SettingsFile: >C:\xxx\FindVUK\config\FindVUK.ini<
2015-09-27 20:12:23 # 23097844 # Information! Passkey MainApp is not valid! >< - please check if it is installed properly!
2015-09-27 20:12:23 # 23097846 # Information! DVDfab MainApp is not valid! >< - please check if it is installed properly!
2015-09-27 20:12:23 # 23097848 # Preferred application is not available
2015-09-27 20:12:23 # 23097850 # MediaPlayer is available!
2015-09-27 20:12:23 # 23097851 # MediaPlayer-MainFile: >C:\Program Files (x86)\xxx\DVDFabMediaPlayer2\FabPlayer.exe<
2015-09-27 20:12:23 # 23097853 # MediaPlayer-LogFile: >C:\Users\xxx\Documents\DVDFab Media Player\\win_player.log<
2015-09-27 20:12:23 # 23097854 # KEYDB-Path: >C:\Users\xxx\AppData\Roaming\aacs<
2015-09-27 20:12:23 # 23097856 # ProcDumpFile: >C:\xxx\FindVUK\tool\procdump.exe<
2015-09-27 20:12:23 # 23097859 # No running application process discovered - start it now >C:\Program Files (x86)\xxx\DVDFabMediaPlayer2\FabPlayer.exe<


The problem I described in my last post occured on September 21st but since you have to be a member for at least 5 days until you can write posts, I posted it today.
Yes, the file does exist but the Windows explorer can't open it with the double backslashes, when I copy the path into the address field. If I use just one, it can open the file just fine.
But no, I can't watch BRs with the media player atm. It did work on September 21st, though.

[nalor]

Released 0.67 - includes only a few changes, one of them is to create a backup of each discovered VUK in the subdirectory VUKbackup, this is to keep a backup of the result including the comment and the title - at the moment those details are lost in case the 'main' keydb.cfg is synchronized to the master-database and there's an older entry of the same disc present in the master-file without title and comment.

I noticed that sometimes even with MediaPlayer and DVDfab9 it happens that the disc is not accessible to validate the VUK - in this case FindVUK will automatically close the application so it can continue without asking the user to close the application.

Finally a small bugfix - the path to the logfile for MediaPlayer and Passkey included a double-backslash, although I never noticed any problems with it, it's corrected now :)

[nalor]

@Neph: I think I've found your problem :)

The default path to the mediaplayer logfile in the ini file seems to be wrong - I just managed to reproduce your problem with a fresh mediaplayer installation :)
What is happening is the following: when you install mediaplayer only a few registry entries are written, for all the other values mediaplayer simply uses it's internal 'default' values.
So directly after a fresh installation of mediaplayer there's no special registry entry to read the 'logfolder' - and as a fallback I use the value from the ini file.
The entry from the ini file looks like this:
%userprofile%\Documents\DVDFab Media Player\Log

but should be this:

%userprofile%\Documents\DVDFab Media Player

To fix your problem you have 2 options:

edit the ini-file and remove the '\log' from the end
open the mediaplayer settings and simply press OK - this way the logfolder entry is written to the registry


In 0.67 the logfile shows a little bit more details about the logfinding process - so I guess when you start the 0.67 without executing step 2 from above you'll find a line like this in the logfile:
2015-09-27 22:49:28 # 377650 # Couldn't read MediaPlayerLogDir from registry - take the info from the ini file

As Mediaplayer isn't working at the moment I'd recommend DVDfab9 to you - as long as you don't use the DVDfab 'main' functions like decoding the content the trial period will never start so it will never expire but nevertheless decrypt the bluray to get the vuk :)

PS: in the next release the default path for the mediaplayer log in the ini file will be correct ;)

[nalor]

Decided to create a new release with the fix immediatly - because it definitely is a show-stopper for first-time users :(

In case the ini-parameter is still set to the wrong entry it's changed to the correct entry.

So 0.68 is now available in the first post.

Kudos to Neph for finding this bug! :thanks:

[avih]

@nalor, v0.68 is detected with 4 threats from 41 engines - https://www.metascan-online.com/#!/results/file/98246bf1f0504754adcd81ec770cfbf3/regular

I hope that these are false positives, but I can't tell for sure and I don't intend to dig into it to find out. I think it'd be best if you could find a proper external host to place your files at.

[nalor]

Hi, just checked your results and as far as i can see 3 of the 4 hits are related to the automatic download of the dump Tool from sysinternals.
Couldnt find details about the last of the 4 results at the moment.
Will check all of them tonight after work.
Regarding the file hoster, i dont care which one i am using. Make a suggestion :-)
I upload every release also directly into the forum, but it takes about a week until the forum file gets the admin approval and this is the reason why i am uploading the file also to a different location.

As i know that there are is no malware hidden in my tool i am sure all 4 hits are false positives.

Will post a hash value for all releases tonight, so everybody can check if his download is really untouched ;-)


Gesendet von meinem D5803 mit Tapatalk

[nalor]

Released 0.70 with a few bugfixes and new features - for details take a look at the first post.

Unfortunately I haven't found time to check for the 4 threats... :(

Edit: I compiled a release where I've simply removed the download option but it didn't make a change - need to check tomorrow what is really the problem with those false positives (in case they find 4 threats in a fresh compiled exe those alerts are false positives for sure... ) so I can also say that the file-hoster file-upload.net isn't respoonsible for those 4 detected problems ...
It has to be something special in the compiler I'm using...

[avih]

Regarding the file hoster, i dont care which one i am using. Make a suggestion :-)


Open source your code, put it on github, and use github releases to host your releases. Or just pay for some host and put up a web page for this application. Or find a free one. Really, up to you.



I upload every release also directly into the forum, but it takes about a week until the forum file gets the admin approval and this is the reason why i am uploading the file also to a different location.


Because admins don't approve attachments daily.



As i know that there are is no malware hidden in my tool i am sure all 4 hits are false positives.


I didn't say it was malware, just that the scan found threats and I don't intend to dig into it. Also, if you had malicious intents (which I believe you don't, but still), then your response would have been the same, something like "yeah, they're all false positives, go ahead and use it".

Bottom line, we don't have the resources to validate which threats are false positives, discuss it with authors which upload executables, and put the time into figuring out whether or not it's actually a threat.

Just find a proper external host for your files, free or payed-for or github, and use it as the main distribution for your releases.

[Sparktank]

If you go open-source, there's also a greater chance that someone might be able to see what's causing the false-positives.

In most cases like this, for freeware tools, it's usually come down to the installer itself.

But, you would need to be more open for others to volunteer to look into things.

I'm no dev, but just what I see in most cases.

[avih]

Ultimately, this is a forum for discussions. It's not a free hosting service for applications, and especially not a free hosting service for closed source applications.

Occasional attachments are fine when they contribute to the discussion, preferably that they're not executable.

We also approve the occasional executable attachment when we feel it's appropriate, maybe because they're posted by credible and respected members of the community, or are some test releases of well known small software packages, or are binaries which are hard to find otherwise because thy're not maintained anymore, or just when we feel it's appropriate.

Your application is being actively developed and you do frequent releases, which is great, but please don't use this forum as the main hosting platform for your close source application.

Discussing it here and posting links to new releases, however, is absolutely fine, and very appropriate.

[nalor]

Just want to report that I've spent some time investigating the 'Malware' issue and my first result is that I've sent false-positive-reports to Baidu and Filseclab.

Finally I've reduced my source to this quite useless piece of code but those 2 engines still detect a threat in it:

Procedure.s Test1(iNumber.i)
ProcedureReturn "result1"
EndProcedure

Procedure.s Test2(iNumber1.i, sString1.s, sString2.s)
Test1(234)
ProcedureReturn "result2"
EndProcedure


Procedure Test2 calls procedure Test1, but Test2 itself is never called... so this does really nothing and is still detected as threat. But when the call from Test2 to Test1 is removed, the compiled result is considered harmless :)
I'm using purebasic 5.31 x86 - just in case you want to reproduce my results.
Test Result of the Metascan (https://www.metascan-online.com/#!/results/file/3d1b64359933486db4be54116881d481/regular)

Unfortunately procedures are quite often called from other procedures in purebasic - so it's really impossible to get a green result in a purebasic application that really does something useful...

So I'm waiting to get feedback from both malware-detection-engines and when they've fine tuned their detection algorithm I'll continue my work to get a 'green' state on https://www.metascan-online.com

Hope this is acceptable for everybody :)

[nalor]

And a few words about the hosting issue and going open source:

The only reason why I'm uploading the files also into the forum because I already noticed that files from older threads that have been uploaded to various other locations on the internet are sometimes really hard to find, very often the original hoster is not available any longer and hopefully a copy of the wanted file can be found with the help of google... so I thought that because my app is really small I simply upload it to forum so it will never get lost ;)

Going open source is still an option - but as the response in the forum here isn't that overwhelming I think the interest in the tool isn't that big at all and as I mentioned already in the first post: reduced to the basics my tool is simply a small convenience-tool that can easily be replaced by 5 minutes of handwork, so in case someone fears that my tool is doing evil things with his computer he should stick with the manual method.

[nalor]

Now I've written also reports for the original findvuk exe file to 3 companies:

Baidy, ByteHero, F-Prot=Cyren (don't know why they're listet as separate engines at the metascan-page).

I'm curios how long it takes to get a response from them - I'll post here when I have news about this topic :)

[avih]

Like I said, judging by your useful previous posts, my guess is that these are false positives and I never suspected you had malicious intents, or else I'd have been much less nice already. However, we just don't have the time/resources/capacity/will to investigate this on every binary attachment or to reproduce binaries which end up as false positive "threats", or to negotiate it with the attachment uploader, etc.

Really, seeing that you already offer it as freeware and it doesn't look to me like you intend to sell it, my best suggestion would be to open source your code such that others could contribute as well, and use whatever platform you choose to also be the main host for your binaries (github, bitbucket, whatever).

[nalor]

I've never done anything with github - so in case I'm going open source I think I would simply include the source into the zip file of the application...

And as the list of features it offers is that short, I can't think of any third party interest to help with development ;)
Apart from that Purebasic as programming-language isn't that wide spread at all - although it's a small application it still has ~5000 lines of code and also uses some winapi functions, so only the commercial purebasic edition can be used to compile the source code.
The main reason for going open source would be to make it easier to understand how the aacs decryption works - basically I think that 'basic' code is easier to read and understand than for example the code of the libaacs-library.

At the moment there's exactly one feature missing I'd like to add:


check in the main-keydb.cfg if the currently detected key is already in the database and if it is check the other values if it makes sense to write a new entry to the file or not.


As soon as this is done development from my side will most likely be reduced to a maintenance mode to check compatibility with new releases of the required external DVDfab applications.

And as long as nobody else is reporting errors or feature request I wouldn't have an idea what else I could integrate ;)

(I thought about a GUI or to limit detection to a fixed drive letter - but decided against it because the tool does at the moment everything it needs to do... and I think it's doing it quite well so no reason to change the workflow fundamentally..)

[avih]

I've never done anything with github - so in case I'm going open source I think I would simply include the source into the zip file of the application...


Using github (and any version control system, and git too) does have a learning curve to it, sometimes even a non trivial one, but I think you could benefit greatly from learning to work within such system.

And as the list of features it offers is that short, I can't think of any third party interest to help with development ;)
Apart from that Purebasic as programming-language isn't that wide spread at all - although it's a small application it still has ~5000 lines of code and also uses some winapi functions, so only the commercial purebasic edition can be used to compile the source code.


That's fine. The mere fact that you host your sources publicly is enough to give it more credit than some arbitrary binary by an unknown(?) developer. Of course, it doesn't guarantee anything, but it would be appreciated by users and developers alike. In your case, I really think it would be a good move.


The main reason for going open source would be to make it easier to understand how the aacs decryption works - basically I think that 'basic' code is easier to read and understand than for example the code of the libaacs-library.


That sounds to me like a good reason indeed.

And while I don't need this tool myself, it does sound to me like a useful tool which is good to have. So do keep up the good work :)

[foxyshadis]

If nothing else, with source included someone else can come along and pick it up years after it's been abandoned, and add their own updates and improvements to it. I've done that a couple of times. Binaries on the forum are iffy, but source is always welcome, especially since external file hosts tend to come and go.

[nalor]

Just want to tell that I got an email from cyren / f-prot:


Following receipt of your False Positive (FP) report, we have identified it to be wrongly detected as a malware. This FP is now fixed, and this file will no longer be detected as malware.


I'm currently on vacation so I cannot verify if the correction is already active.


Gesendet von meinem D5803 mit Tapatalk

[candela]

Version 0.70 fails to validate the VUK even though it is valid. Appears to happen with all discs


2015-10-03 16:09:05 # 1207999 # DVDfab_GetVukFromDump - File >C:\Utils\FindVUK_0.70\dump\6915989258FC4C802F37198172DA6F89E2B9B488_BARBARELLA..dmp< DiscID >6915989258FC4C802F37198172DA6F89E2B9B488< Offset_Folder_DiscId >0x114< Offset_DiscId_Vuk >0x5F<
2015-10-03 16:09:06 # 1208467 # ------------------------------------
2015-10-03 16:09:06 # 1208473 # VolumeName: BARBARELLA
2015-10-03 16:09:06 # 1208478 # DiscID : 6915989258FC4C802F37198172DA6F89E2B9B488
2015-10-03 16:09:06 # 1208483 # VUK : 2C71BCD772B0567DAF39B3BB9F4A2796
2015-10-03 16:09:06 # 1208488 # ------------------------------------
2015-10-03 16:09:06 # 1208496 # AACS folder on disc is reachable - ValidateVUK is possible
2015-10-03 16:09:06 # 1208502 # AACS folder on bluray is reachable!
2015-10-03 16:09:06 # 1208526 # Information: preferred Bluray-MetaTitle language found >Barbarella<
2015-10-03 16:09:06 # 1208545 # FeatureDescriptor :00 00 00 0C 00 00 00 40 01 0D 01 04 01 01 01 01
2015-10-03 16:09:06 # 1208550 # AacsVersion :1
2015-10-03 16:09:06 # 1208555 # AacsActive :1
2015-10-03 16:09:06 # 1208559 # BindingNonceGenSupp :1
2015-10-03 16:09:06 # 1208564 # BindingNonceBlockCnt :1
2015-10-03 16:09:06 # 1208568 # BusEncryptionSupp :0
2015-10-03 16:09:06 # 1208572 # ReadDriveCertificate :0
2015-10-03 16:09:06 # 1208576 # AgidCount :1
2015-10-03 16:09:06 # 1208580 # Get UnitKeys
2015-10-03 16:09:06 # 1208594 # UnitKeyCount >7<
2015-10-03 16:09:06 # 1208598 # >>> UnitKey: 584FDD75AD8BC136BCD829CFD7F0B90C
2015-10-03 16:09:06 # 1208603 # >>> UnitKey: 12B4D0D990284F4D1B94DE7846E8BAA7
2015-10-03 16:09:06 # 1208608 # >>> UnitKey: A828A551C4BCCE2E05B677683C053236
2015-10-03 16:09:06 # 1208613 # >>> UnitKey: 89A4C27DD1FFE6F49A2ECE0C73DB2F5A
2015-10-03 16:09:06 # 1208619 # >>> UnitKey: AE14752A7489779F9AD15152C8C825B9
2015-10-03 16:09:06 # 1208625 # >>> UnitKey: 0E0A2EE4398919D0D544B2D08A6F07F2
2015-10-03 16:09:06 # 1208631 # >>> UnitKey: 9FDA1562148C2A9B5CCB8FC6506EB7CB
2015-10-03 16:09:06 # 1209141 # File >F:\BDMV\STREAM\00011.m2ts< is encrypted!
2015-10-03 16:09:06 # 1209146 # ERROR! Validation of VUK failed >0<


Version 0.68 works fine


2015-10-03 16:22:13 # 1980482 # DVDfab_GetVukFromDump - File >C:\Utils\FindVUK_0.68\dump\6915989258FC4C802F37198172DA6F89E2B9B488_BARBARELLA..dmp< DiscID >6915989258FC4C802F37198172DA6F89E2B9B488< Offset_Folder_DiscId >0x114< Offset_DiscId_Vuk >0x5F<
2015-10-03 16:22:14 # 1980977 # ------------------------------------
2015-10-03 16:22:14 # 1980983 # VolumeName: BARBARELLA
2015-10-03 16:22:14 # 1980988 # DiscID : 6915989258FC4C802F37198172DA6F89E2B9B488
2015-10-03 16:22:14 # 1980993 # VUK : 2C71BCD772B0567DAF39B3BB9F4A2796
2015-10-03 16:22:14 # 1980998 # ------------------------------------
2015-10-03 16:22:14 # 1981071 # AACS folder on disc is reachable - ValidateVUK is possible
2015-10-03 16:22:14 # 1981079 # AACS folder on bluray is reachable!
2015-10-03 16:22:14 # 1981089 # Information: no bdmv-meta-dl directory available on disc - cannot read meta-title (-6)
2015-10-03 16:22:15 # 1981640 # FeatureDescriptor :00 00 00 0C 00 00 00 40 01 0D 01 04 01 01 01 01
2015-10-03 16:22:15 # 1981645 # AacsVersion :1
2015-10-03 16:22:15 # 1981649 # AacsActive :1
2015-10-03 16:22:15 # 1981652 # BindingNonceGenSupp :1
2015-10-03 16:22:15 # 1981657 # BindingNonceBlockCnt :1
2015-10-03 16:22:15 # 1981661 # BusEncryptionSupp :0
2015-10-03 16:22:15 # 1981665 # ReadDriveCertificate :0
2015-10-03 16:22:15 # 1981668 # AgidCount :1
2015-10-03 16:22:15 # 1981673 # Get UnitKeys
2015-10-03 16:22:15 # 1981685 # UnitKeyCount >7<
2015-10-03 16:22:15 # 1981691 # >>> UnitKey: 584FDD75AD8BC136BCD829CFD7F0B90C
2015-10-03 16:22:15 # 1981697 # >>> UnitKey: 12B4D0D990284F4D1B94DE7846E8BAA7
2015-10-03 16:22:15 # 1981702 # >>> UnitKey: A828A551C4BCCE2E05B677683C053236
2015-10-03 16:22:15 # 1981708 # >>> UnitKey: 89A4C27DD1FFE6F49A2ECE0C73DB2F5A
2015-10-03 16:22:15 # 1981713 # >>> UnitKey: AE14752A7489779F9AD15152C8C825B9
2015-10-03 16:22:15 # 1981719 # >>> UnitKey: 0E0A2EE4398919D0D544B2D08A6F07F2
2015-10-03 16:22:15 # 1981724 # >>> UnitKey: 9FDA1562148C2A9B5CCB8FC6506EB7CB
2015-10-03 16:22:15 # 1982235 # Decrypted first unit of file >F:\BDMV\STREAM\00011.m2ts< with UnitKey >1<
2015-10-03 16:22:15 # 1982241 # Validation successful! VUK is valid!!
2015-10-03 16:22:15 # 1982252 # -------------------------------------------------------
2015-10-03 16:22:15 # 1982257 # VolumeName: BARBARELLA
2015-10-03 16:22:15 # 1982262 # DiscID : 6915989258FC4C802F37198172DA6F89E2B9B488
2015-10-03 16:22:15 # 1982266 # VUK : 2C71BCD772B0567DAF39B3BB9F4A2796
2015-10-03 16:22:15 # 1982271 # MKBrev : 31
2015-10-03 16:22:15 # 1982277 # BusEncrEn : 0
2015-10-03 16:22:15 # 1982282 # -------------------------------------------------------

[nalor]

You're right... once again I managed to release a more or less unuseable version :(

[nalor]

Posted a hopefully bugfree release 0.71 in the first post.

A little bit more details about the changes than in the first post:

1) to detect if a file on the disc is encrypted or not I need to read a byte from this file and check for the encryption flag - before releasing 0.70 I noticed that in my virtual machine this detection didn't work as expected.. so I checked for the reason and found this: basically my bluray-optical-drive that is connected as passthrough device into the virtual machine isn't working any longer - don't know why, but it's not possible to read a file from a bluray in the drive.
But FindVUK didn't detect an error when reading from the file - and finally I've found this: purebasic-readbyte command (http://www.purebasic.com/documentation/file/readbyte.html) - this command returns '0' in case of an error, and also '0' in case a '0' byte has been successfully read from the file, so finally there's no way to detect if an error occured or the read byte is zero.. strange thing.
This was the reason to change the related procedure in FindVUK from the integrated purebasic to a few winapi commands so I can properly detect read errors when reading the disc - unfortunately I introduced a stupid error when changing this: because of the options to detect errors I've changed the return values of the procedure and missed to adopt all related parts accordingly.
So finally it always ended in an error in case an encrypted file has been found to validate the vuk... I've no idea why I didn't notice this before releasing... stupid me :(


2) because of this false positive malware topic I tried to remove all procedures from the application that are never called by anything. In case you're wondering why there are such procedures in the application: to make things easier I have a couple of include-files that contain different procedures for a certain topic, usually only a fraction of them is really used in the application, but as the purebasic compiler doesn't make a difference if something is really used or not all procedures from those include files are compiled and find their way into the final exe file.
In the past I've used this include file here for registry access: Registry_Include.pbi (http://purearea.net/pb/CodeArchiv/Includes+Macros/Includes/Registry_Include.pbi) - this has everything you need to get easy access to the registry :) But as I only read from the registry in FindVUK I've removed all procedures that are used to write to the registry and also those parts from the 'read' procedures that are used to read from foreign computers through the network.
Finally the compiled exe is now approx. 7kB smaller than before, but it didn't change anything about the malware topic... still 4 of 43 find something suspicious in my application :( grrr :(

[nalor]

Noticed that AACS updater ignores all lines with the additional date-entry, so I've immediatly created a 0.72 where it's possible to use an ini switch to enable the date entry that is by default set to off.

[candela]

The latest Vivaldi browser version now warns me findVUK_x.zip is malicious and has been blocked when I download. Not sure what's going on there...

[nalor]

Whats a vivaldi Browser?

Gesendet von meinem D5803 mit Tapatalk

[candela]

Whats a vivaldi Browser?

Gesendet von meinem D5803 mit Tapatalk

The new browser (https://vivaldi.com) from some former Opera employees. It's based on Chrome so I assume that will give similar warnings. Not sure how it checks downloads

[nalor]

Just installed vivaldi and tried to download this file - and you're right about this 'malicous' message ;)

But honestly vivaldi isn't scanning the file but simply blacklisting everything from file-upload.net ... (see here: Vivaldi Forum about 'malicicous' message (https://vivaldi.net/en-US/forum/vivaldi-browser/3177-shining-new-snapshot-1-0-161-2-more-bugfixing#25274)

And this was the first time ever I've seen how much advertising is on the file-uploaded page.. wow (usually I'm using an adblocker in firefox so I've never noticed how bad this page really is.... ).

I'm currently finishing my final release and will check which other file-hoster is an option with little to none annoying ads on the page...