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.

 

Go Back   Doom9's Forum > General > Decrypting

Reply
 
Thread Tools Search this Thread Display Modes
Old 6th February 2018, 20:46   #261  |  Link
nalor
Registered User
 
Join Date: Dec 2013
Posts: 359
Quote:
Originally Posted by candela View Post
Shouldn't you simply discard data from a virtual drive? Or you cannot detect it's virtual? All the other FindVUK data cannot be verified/trusted either if it's not the original disc
I don't think that supporting virtual drives can cause any issues - and basically the difference between real and virtual drives is 288sectors * 2048bytes = 576KB - compared to the real size of the volume this 'error' is negligible.
Or what do you think?
nalor is offline   Reply With Quote
Old 6th February 2018, 20:51   #262  |  Link
candela
Registered User
 
Join Date: Jun 2005
Posts: 177
Quote:
Originally Posted by nalor View Post
I don't think that supporting virtual drives can cause any issues - and basically the difference between real and virtual drives is 288sectors * 2048bytes = 576KB - compared to the real size of the volume this 'error' is negligible.
Or what do you think?
I mean how can you be sure the files in the ISO are identical to the originals ? This would also make it possible to upload fake data.
candela is offline   Reply With Quote
Old 6th February 2018, 23:01   #263  |  Link
BRC85sYrg
Registered User
 
Join Date: Feb 2017
Posts: 9
Quote:
Originally Posted by candela View Post
so later we can make a database of BD+ tables, similar to keydb.cfg for keys. The ultimate goal will be real-time playback of BD+ protected titles using VLC. We just need to find a decent C programmer to update Videolan's libbdplus to load these tables
thanks for your explanation, thats a nice goal


Quote:
Originally Posted by nalor View Post
Just released 1.08 - fixes the Problem with CloseOnExit, decrypts the UnitKeys earlier so they are written to keydb.cfg even in case the VUK cannot be validated ...
thank you very much for this update! dumping Unit Keys works now perfectly with BEE drives.


Quote:
Originally Posted by BRC85sYrg View Post
some suggestions for the next release:
- "VOLUME_ID" as an additional MeaninglessVolumeName in the config file
@nalor maybe you oversaw this suggestion, so I posted it again.


Quote:
Originally Posted by candela View Post
I mean how can you be sure the files in the ISO are identical to the originals ? This would also make it possible to upload fake data.
fake data uploads can't be prevent.
@nalor without virtual drive support will it still be possible to pass-trough a drive to a virtual machine?
BRC85sYrg is offline   Reply With Quote
Old 7th February 2018, 21:46   #264  |  Link
nalor
Registered User
 
Join Date: Dec 2013
Posts: 359
Quote:
Originally Posted by BRC85sYrg View Post
@nalor maybe you oversaw this suggestion, so I posted it again.

fake data uploads can't be prevent.
@nalor without virtual drive support will it still be possible to pass-trough a drive to a virtual machine?

you're right - I missed your suggestion, will change it with the next release.

I don't have any plans to limit support to real-drives ... it wouldn't make any difference - in case someone creates a modified iso-file he just needs to burn it to a disc and voila it would be supported.

Basically FindVUK reads data from the memory of DVDfab products -> only discs recognized by this apps are possible and manually created iso files and/or discs will very likely always fail.

So I just leave everything as it is
nalor is offline   Reply With Quote
Old 15th February 2018, 14:36   #265  |  Link
TTide
Registered User
 
Join Date: Jul 2014
Posts: 25
FindVUK 1.08 Bug

I failed to get the VUK for my disc. Some bug i found in FindVUK 1.08, as i was able to get it in FindVUK 1.07.

Code:
2018-02-15 14:28:30 # 0 # [I] main / legacy / #############################################################################
2018-02-15 14:28:30 # 0 # [I] main / legacy /  ----------- FindVUK 1.08 ----------- 
2018-02-15 14:28:30 # 0 # [I] main / legacy / Operating System: Windows 10
2018-02-15 14:28:30 # 1 # [I] main / legacy / SettingsFile: >C:\FindVUK_1.08\config\FindVUK.ini<
2018-02-15 14:28:30 # 4 # [I] main / legacy / Current BufferSize 120 x 9001 - ScreenSize 120 x 30
2018-02-15 14:28:30 # 5 # [I] main / legacy / Requested BufferSize 120 x 300 - ScreenSize 120 x 50
2018-02-15 14:28:30 # 5 # [I] main / legacy / Max. ScreenSize 240 x 72
2018-02-15 14:28:30 # 29 # [I] main / legacy / Final New Values - BufferSize 120 x 9001 - ScreenSize 120 x 50 - Resize >1<
2018-02-15 14:28:30 # 29 # [I] main / legacy / M1 - New BufferSize 120 x 9001
2018-02-15 14:28:30 # 29 # [I] main / legacy / Mx2 - New ScreenSize 120 x 50
2018-02-15 14:28:30 # 32 # [I] main / legacy / Information! Passkey MainApp is not valid! ><
2018-02-15 14:28:30 # 32 # [I] main / legacy / Information! MediaPlayer MainApp is not valid! ><
2018-02-15 14:28:30 # 33 # [I] main / legacy / Untested DVDfab Version >0.0.0.0< found
2018-02-15 14:28:30 # 34 # [I] main / legacy / Preferred application is not available
2018-02-15 14:28:30 # 34 # [I] main / legacy / DVDfab is available!
2018-02-15 14:28:30 # 34 # [I] main / legacy / DVDfab-MainFile:      >C:\Program Files (x86)\DVDFab 10\DVDFab.exe<
2018-02-15 14:28:30 # 34 # [I] main / legacy / DVDfab-LogFile:       >C:\Users\gamer\Documents\DVDFab10\Log\dvdfab_internal.log<
2018-02-15 14:28:30 # 34 # [I] main / legacy / DVDfab-CloseAtTheEnd>1<
2018-02-15 14:28:30 # 34 # [I] main / legacy / KEYDB-Path:           >C:\Users\gamer\AppData\Roaming\aacs\<
2018-02-15 14:28:30 # 35 # [I] main / legacy / KEYDB-Backup-Path:    >C:\FindVUK_1.08\VUKbackup\<
2018-02-15 14:28:30 # 35 # [I] main / legacy / ProcDumpFile:         >C:\FindVUK_1.08\tool\procdump.exe<
2018-02-15 14:28:30 # 35 # [I] main / legacy /  --- PART 1 --- GET VUK ---
2018-02-15 14:28:30 # 39 # [I] main / legacy / No running application process discovered
2018-02-15 14:28:30 # 39 # [I] main / legacy /  >> Start it now >C:\Program Files (x86)\DVDFab 10\DVDFab.exe<
2018-02-15 14:28:32 # 1856 # [I] main / legacy / Untested DVDfab App Version found ><
2018-02-15 14:28:32 # 1856 # [I] main / legacy / Value set in ini file will be used for 'Folder2DiscID'
2018-02-15 14:28:32 # 1856 # [I] main / legacy / Value set in ini file will be used for 'Folder2VUK'
2018-02-15 14:28:32 # 1856 # [I] main / legacy / Offset Folder2DiscId >0x114< - Folder2Vuk >0x173<
2018-02-15 14:28:43 # 12665 # [I] main / legacy / Drive opened
2018-02-15 14:28:43 # 12666 # [I] main / legacy / DiscType detected >Blu-ray BDMV<
2018-02-15 14:28:43 # 12666 # [I] main / legacy / Volume Label detected >Deadpool<
2018-02-15 14:28:56 # 25581 # [I] main / legacy / DriveLetter detected >E<
2018-02-15 14:28:59 # 28604 # [I] main / legacy / Detected CopyProtections AACS >1< BD+ >1<
2018-02-15 14:29:11 # 40103 # [I] main / legacy / DiscID found >CFC68F3D31093942BE12908CED8C02C4494F1C5E<
2018-02-15 14:29:37 # 66597 # [I] main / legacy / MainPlaylist found >00800.mpls<
2018-02-15 14:29:45 # 74754 # [I] main / legacy / DVDfab got VUK - create memdump now!
2018-02-15 14:29:45 # 74876 # [I] main / legacy /  DUMP >>> 
2018-02-15 14:29:45 # 74876 # [I] main / legacy /  DUMP >>> ProcDump v9.0 - Sysinternals process dump utility
2018-02-15 14:29:45 # 74877 # [I] main / legacy /  DUMP >>> Copyright (C) 2009-2017 Mark Russinovich and Andrew Richards
2018-02-15 14:29:45 # 74877 # [I] main / legacy /  DUMP >>> Sysinternals - www.sysinternals.com
2018-02-15 14:29:45 # 74877 # [I] main / legacy /  DUMP >>> 
2018-02-15 14:29:45 # 74878 # [I] main / legacy /  DUMP >>> No process matching the specified name can be found.
2018-02-15 14:29:45 # 74878 # [I] main / legacy /  DUMP >>> Try elevating the command prompt or using PsExec to make one as SYSTEM.
2018-02-15 14:29:45 # 74878 # [I] main / legacy /  DUMP >>> 	psexec.exe -s -d -i cmd.exe
2018-02-15 14:29:45 # 74879 # [I] main / legacy /  DUMP >>> 	procdump.exe -accepteula ...
2018-02-15 14:29:45 # 74879 # [I] main / legacy /  DUMP >>> 
2018-02-15 14:29:45 # 74880 # [I] main / legacy / ERROR!! Exitcode >-2< - Dump failed! - Program >C:\FindVUK_1.08\tool\procdump.exe< Parameter > -ma -o DVDFab.exe "C:\FindVUK_1.08\dump\CFC68F3D31093942BE12908CED8C02C4494F1C5E_Deadpool.dmp"<
2018-02-15 14:29:45 # 74880 # [I] main / legacy / Error during process memory dump >C:\FindVUK_1.08\dump\CFC68F3D31093942BE12908CED8C02C4494F1C5E_Deadpool.dmp<
2018-02-15 14:29:45 # 74881 # [I] main / legacy / Error during process memory dump - please report in the doom9 forum!
2018-02-15 14:29:45 # 74884 # [I] main / legacy / ERROR! Couldn't create memory dump! Exit application!
2018-02-15 14:29:45 # 74896 # [I] main / legacy / CloseAtTheEnd is active, but no running application >C:\Program Files (x86)\DVDFab 10\DVDFab.exe< could be found
TTide is offline   Reply With Quote
Old 15th February 2018, 21:36   #266  |  Link
nalor
Registered User
 
Join Date: Dec 2013
Posts: 359
Hi! I've no idea what really happens in your case - it already starts at the beginning of the logfile:

Quote:
Untested DVDfab Version >0.0.0.0< found
Which DVDfab version are you using?
nalor is offline   Reply With Quote
Old 16th February 2018, 22:51   #267  |  Link
nalor
Registered User
 
Join Date: Dec 2013
Posts: 359
Just released 1.09 - it fixes a few DVDfab related bugs I've found during the investigation of @TTide s problem - but I've still no idea why 1.07 is working for him and 1.08 isn't.
nalor is offline   Reply With Quote
Old 17th February 2018, 17:35   #268  |  Link
TTide
Registered User
 
Join Date: Jul 2014
Posts: 25
My DVDfab Version is 10.0.7.7 and FindVUK 1.09 also fails to create a Dump. I keep getting this:
Quote:

2018-02-17 17:29:21 # 54896 # [I] main / legacy / DVDfab got VUK - create memdump now!
2018-02-17 17:29:21 # 55003 # [I] main / legacy / DUMP >>>
2018-02-17 17:29:21 # 55003 # [I] main / legacy / DUMP >>> ProcDump v9.0 - Sysinternals process dump utility
2018-02-17 17:29:21 # 55004 # [I] main / legacy / DUMP >>> Copyright (C) 2009-2017 Mark Russinovich and Andrew Richards
2018-02-17 17:29:21 # 55004 # [I] main / legacy / DUMP >>> Sysinternals - www.sysinternals.com
2018-02-17 17:29:21 # 55004 # [I] main / legacy / DUMP >>>
2018-02-17 17:29:21 # 55004 # [I] main / legacy / DUMP >>> No process matching the specified name can be found.
2018-02-17 17:29:21 # 55005 # [I] main / legacy / DUMP >>> Try elevating the command prompt or using PsExec to make one as SYSTEM.
2018-02-17 17:29:21 # 55005 # [I] main / legacy / DUMP >>> psexec.exe -s -d -i cmd.exe
2018-02-17 17:29:21 # 55005 # [I] main / legacy / DUMP >>> procdump.exe -accepteula ...
2018-02-17 17:29:21 # 55005 # [I] main / legacy / DUMP >>>
TTide is offline   Reply With Quote
Old 17th February 2018, 20:51   #269  |  Link
nalor
Registered User
 
Join Date: Dec 2013
Posts: 359
Quote:
Originally Posted by TTide View Post
My DVDfab Version is 10.0.7.7 and FindVUK 1.09 also fails to create a Dump. I keep getting this:
Your main problem is that DVDfab 10.0.7.7 does not work any longer - you have to downgrade to DVDfab 10.0.4.8 - this is the latest release that is compatible with FindVUK.

Usually FindVUK should automatically detect that your release is not compatible and should exit, but I did it wrong - corrected it now for the next release.

On the other hand something is still strange - I still don't know why you're getting version 0.0.0.0.
Does it still display version 0.0.0.0 even with findVUK 1.09 ?
nalor is offline   Reply With Quote
Old 18th February 2018, 00:16   #270  |  Link
candela
Registered User
 
Join Date: Jun 2005
Posts: 177
new ini help file. Hopefully everything is explained correctly
candela is offline   Reply With Quote
Old 18th February 2018, 19:43   #271  |  Link
TTide
Registered User
 
Join Date: Jul 2014
Posts: 25
Quote:
Originally Posted by nalor View Post
Your main problem is that DVDfab 10.0.7.7 does not work any longer - you have to downgrade to DVDfab 10.0.4.8 - this is the latest release that is compatible with FindVUK.

Usually FindVUK should automatically detect that your release is not compatible and should exit, but I did it wrong - corrected it now for the next release.

On the other hand something is still strange - I still don't know why you're getting version 0.0.0.0.
Does it still display version 0.0.0.0 even with findVUK 1.09 ?
No it displays this now:

Tested DVDfab Version >10.0.4.8< found
TTide is offline   Reply With Quote
Old 18th February 2018, 23:17   #272  |  Link
candela
Registered User
 
Join Date: Jun 2005
Posts: 177
I just noticed there are serious problems with the dates (1.09 and before)

For example Predator:
<DiscId Date="2010-03-20">AA5B2D0735BF048400155066E30221C5ABB12AB4</DiscId>

Correct date:
2010-04-27 18-38-34 A---R--- 65.536 Unit_Key_RO.inf

There is not a single file on this disc with date 2010-03-20

<BDplus Date="2010.04.28">1</BDplus>
Again, there's not a single file on the disc with this date

The BDSVM dir is also dated 2010-04-27. BDSVM files
2009-10-15 19-42-20 A---R--- 20.971.520 00000.svm

I think
- for discid use date of unit_key_ro.inf
- for BD+ date , same as DiscID or folder BDSVM (not sure if it's ever different)

Note: makemkv reports Timestamp: 2010-04-27 10:46:49 for this disc, don't know where that time is coming from
candela is offline   Reply With Quote
Old 19th February 2018, 10:37   #273  |  Link
nalor
Registered User
 
Join Date: Dec 2013
Posts: 359
Quote:
Originally Posted by candela View Post
I think
- for discid use date of unit_key_ro.inf
- for BD+ date , same as DiscID or folder BDSVM (not sure if it's ever different)

Note: makemkv reports Timestamp: 2010-04-27 10:46:49 for this disc, don't know where that time is coming from
Currently I'm using the creation-date of unit_key_ro.inf for the discid-date (I thought this makes more sense than using the last-modified date ?? ) - but the spec is not clear in this point, so just tell me if I should change it.

The date used for the BD+ date is stored inside the file itself - has nothing to do with the creation/last-modified or last-accessed dates as reported by windows. (I read the first 18 bytes of \BDSVM\00000.svm and get the date as visible here: libbdplus loader.c
nalor is offline   Reply With Quote
Old 19th February 2018, 11:23   #274  |  Link
candela
Registered User
 
Join Date: Jun 2005
Posts: 177
Quote:
Originally Posted by nalor View Post
Currently I'm using the creation-date of unit_key_ro.inf for the discid-date (I thought this makes more sense than using the last-modified date ?? ) - but the spec is not clear in this point, so just tell me if I should change it.

The date used for the BD+ date is stored inside the file itself - has nothing to do with the creation/last-modified or last-accessed dates as reported by windows. (I read the first 18 bytes of \BDSVM\00000.svm and get the date as visible here: libbdplus loader.c
Aha, maybe that's also why I have been seeing sometimes 1 day differences when comparing different sources for the disc date, I will investigate and check also the original doom9 posts. Maybe store both?

I didn't know BD+ actually had the date internally stored, thanks for this new information

Why the different formats though "-" vs "."
candela is offline   Reply With Quote
Old 19th February 2018, 20:23   #275  |  Link
nalor
Registered User
 
Join Date: Dec 2013
Posts: 359
Quote:
Originally Posted by candela View Post
Why the different formats though "-" vs "."
The libaacs spec says the delimiter character has to be '-', this is the reason why it is not '.' for the DiscId date
nalor is offline   Reply With Quote
Old 19th February 2018, 22:15   #276  |  Link
nalor
Registered User
 
Join Date: Dec 2013
Posts: 359
Quote:
Originally Posted by nalor View Post
The libaacs spec says the delimiter character has to be '-', this is the reason why it is not '.' for the DiscId date
I'll change the - to . with the next release! I just noticed that there's no need to follow the keydb-spec inside the MetaXML file
nalor is offline   Reply With Quote
Old 4th March 2018, 22:19   #277  |  Link
candela
Registered User
 
Join Date: Jun 2005
Posts: 177
Quote:
Originally Posted by nalor View Post
Just released 1.08 - fixes a stupid bug I noticed when I checked the MetaXML files I've uploaded into the online-db: in case a few discs are uploaded one after the other, the 2nd disc includes 2 hashed, the 3rd disc 3 of them ... and so on. never cleared the previous hash values in 1.07
problem still exists in version 1.09 for MetaTitles. if the second disc does not have any metatitles, it's using the metatitle from the previous disc

too many bugs nalor, more testing ! better check all the other fields in this scenario

Last edited by candela; 4th March 2018 at 22:58.
candela is offline   Reply With Quote
Old 4th March 2018, 22:36   #278  |  Link
nalor
Registered User
 
Join Date: Dec 2013
Posts: 359
Quote:
Originally Posted by candela View Post
problem still exists in version 1.09 for MetaTitles. if the second disc does not have any metatitles, it's using the metatitle from the previous disc

too many bugs nalor, more testing ! better check all the other fields in this scenario
Also noticed this 2nd bug 2 days ago....

Will release a new version hopefully tomorrow.

Gesendet von meinem E5823 mit Tapatalk
nalor is offline   Reply With Quote
Old 4th March 2018, 22:45   #279  |  Link
candela
Registered User
 
Join Date: Jun 2005
Posts: 177
1) some more bad volume labels

BLURAY, blu-ray-pc, DISC_TITLE BD1, DISC_TITLE BD2, DISC, _YOUR_DISC_LABEL_, DISC1, DISC2, BD_ROM, SPE_BDLIVE, BD_VIDEO, PS3VOLUME



2) bad meta titles

BLU-RAY AUDIO, BLU-RAY 3D, BLU-RAY, Blu-ray, Blu-ray™, BLU-RAY VIDEO

also chars (utf-8): 0x2e, 0x20, 0x20 0x20 0x20 0x20 0x20, 0xc2 0xa0


3) xmls aren't generated when upload is disabled. probably by design but may be reconsider? xmls can then be generated offline and uploaded later


4) maybe add Batchfiles for the sychronize and GetMetaInfoFromDisc modes


5) how about auto start GetMetaInfoFromDisc in case no or bad verson of dvdfab is detected

Last edited by candela; 5th March 2018 at 18:10.
candela is offline   Reply With Quote
Old 5th March 2018, 22:27   #280  |  Link
nalor
Registered User
 
Join Date: Dec 2013
Posts: 359
Quote:
Originally Posted by candela View Post
1) some more bad volume labels

BLURAY, blu-ray-pc, DISC_TITLE BD1, DISC_TITLE BD2, DISC, _YOUR_DISC_LABEL_, DISC1, DISC2, BD_ROM, SPE_BDLIVE, BD_VIDEO, PS3VOLUME



2) bad meta titles

BLU-RAY AUDIO, BLU-RAY 3D, BLU-RAY, Blu-ray, Blu-ray™, BLU-RAY VIDEO

also chars (utf-8): 0x2e, 0x20, 0x20 0x20 0x20 0x20 0x20, 0xc2 0xa0


3) xmls aren't generated when upload is disabled. probably by design but may be reconsider? xmls can then be generated offline and uploaded later


4) maybe add Batchfiles for the sychronize and GetMetaInfoFromDisc modes


5) how about auto start GetMetaInfoFromDisc in case no or bad verson of dvdfab is detected

Hi!

I've added BLURAY to the list of meaningless volumenames - but I don't think it makes sense to add the other names also. Currently there are ~1100 entries in the onlinedatabase and the other titles are not in the list, so I don't think it's really necessary to add them.
Same for the meta-titles - none of them from your list above is in my list and I don't think it's helpful to add such special titles to the list.
When I check the titles in the database I also find a couple that really look meaningless to me - but those are specials that only occur 1 time.

XML creation: changed the behaviour, MetaXML is always created now - but currently I have no plans to allow a manual upload into the online database.

Batchfiles: I will think about it, maybe when the onlinedb is really functional and the synchronisation is correctly working

Automatic GetMeta: will also think about it - but honestly I still don't know why we should collect this data at all?
nalor is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 01:53.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.