Hello,
I've rewritten the application. The initial post was updated. Wine isn't needed anymore, since they published a native linux version for DVDFab. The principle of my application stayed the same but it's now easier accessible. All instructions can be found on the github project page. It also contains precompiled binaries.
I also verified the directly-dump-extraction feature with the spiderman dumps on mediafire regarding the PID in the dump's filename with procdump.exe. (see nalor's post)
Quote:
Originally Posted by Wilbert
Please don't remove such threads, even if you get no meaningful response.
|
I'm sorry for deleting this post, but with the older versions, some bugs came up and i haven't had enough time to fix them, so i decided to remove this post, before taking any further steps.
Quote:
Originally Posted by candela
Download link is no longer valid
In the latest AACSUpdater Keydb.cfg we are already getting differences with FindVUK. Can you verify?
0xC42F053D739BA7DA1778C34780DD6EE960F56461 = The Boy | V | 0x595DF4860A2254B4D97C7FF8CF217052 ; vukextract v0.1.8
0xC42F053D739BA7DA1778C34780DD6EE960F56461 = The Boy (The Boy) | V | 0xA0FE77D06951C86560EB419F520554E9 ; MKBv61/FindVUK 1.02
|
Thank you. I'm 99% sure that the VUK from vukextract is wrong, because there was a bug which suddenly messed up the keys. This is fixed in the v1.0.0 release. I did not expect, that somebody would submit keys in this early stage of the application without testing them properly... Sorry for that.
Besides, I have to point out that my application prints the DiscID, Title, VUK, MediaKey and VolumeID. The VUK can be calculated from the MediaKey and VolumeID to verify it (as in my application) "easily". But verifying submitted keys in the labdv KEYDB.cfg is not possible since only fields for VUK and DiscID are available and the other ones are omitted.