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. |
14th January 2007, 06:34 | #741 | Link | |
Registered User
Join Date: Nov 2001
Posts: 11
|
Quote:
|
|
14th January 2007, 06:52 | #745 | Link | |
Registered User
Join Date: Oct 2003
Posts: 435
|
Quote:
works great here to show the hash thx Code:
Backup HD-DVD V1.00 (OQ Mod 0.1) Starting Testing source Found valid HD-DVD source. Disc Hash: 0E75082678AAD5CD4410A28A662D6832D21EB325 Look for this movie in my database Found movie: King Kong Start backup on Sat Jan 13 21:50:06 PST 2007 Scaning video directory Processing BLACK.EVO key = 3 Code:
B5DE266362701D2E7C36A5F389855F2B7DB6A17F=waterworld |V|0/13/2007|00000000000000000000000000000000 Last edited by woah!; 14th January 2007 at 07:03. |
|
14th January 2007, 07:02 | #746 | Link | |
Registered User
Join Date: Jan 2007
Posts: 28
|
Quote:
3.1 Device Keys Each compliant device is given a set of secret Device Keys when manufactured. These Device Keys, referred to as Kd_i (i=0,1,…,n-1), are provided by AACS LA, and are used by the device to process the MKB to calculate Km (Media Key). 1.8 Terminology Media Key A key that is used to unlock the Title Keys stored on a media that contains Titles protected by AACS. The Media Key can be computed by successfully processing a MKB. |
|
14th January 2007, 09:50 | #748 | Link |
Registered User
Join Date: Mar 2006
Posts: 272
|
as a side note,i thought this was an interesting comment as regards HDDVD/BR
Flash will kill Blu-ray and HD DVD http://uk.theinquirer.net/?article=36930 flash memory is all well and good but i find it iritating that the superslow USB became the standard for interfacing it. its about time we had a FAR faster interface so as to get far better read/write from any flash device ,it seems we need at the very least an updated far faster USB3 to be introduced and PDQ... Last edited by popper; 14th January 2007 at 09:59. |
14th January 2007, 11:05 | #750 | Link |
Country Member
Join Date: Sep 2004
Location: is everything!
Posts: 6,499
|
@popper
Apparently you do not read what Doom9 and I write. Strike issued. Stick to the topic. "Interesting" things between BR/HDDVD do not belong in this thread. Regards
__________________
Les Only use genuine Verbatim or Taiyo Yuden media. |
14th January 2007, 11:15 | #751 | Link |
Registered User
Join Date: Jan 2007
Posts: 117
|
unable to access jarfile backuphddvd.jar error
hi guys,
first post here. i don't like this java thing, everytime i try to start backuphddvd it says "unable to access jarfile backuphddvd.jar". What i have to do? i have jre 1.4.2, jre 1.6.0 and jre 1.5.0.10 but everytime i get the same error. It would be helpful to make a tool without java! thank you very much. regards |
14th January 2007, 12:12 | #752 | Link |
Registered User
Join Date: Nov 2001
Posts: 50
|
About player revocation for when new discs are out...
I was wondering, how is a player identified as being that exact one?. if the version string is somehow sent back to the player then cant we simply edit the .exes resources to send back the vesion of the newly released player?. e.g. if you use powerdvd6.5 and then 7 is released with 6.5 being the "revoked" one. Would it not be feasible to alter 6.5 to report back as 7? I'm unsure if there are any checksums returned as part of the return message but was just wondering.. |
14th January 2007, 12:16 | #753 | Link | |
Registered User
Join Date: Jan 2002
Posts: 155
|
Quote:
BTW has windvd responded to anything yet lol? |
|
14th January 2007, 13:08 | #755 | Link |
Registered User
Join Date: Jan 2007
Posts: 22
|
I was wondering about that, is it not possible to create a revocation list, with say one player key in it that no one cares about, and set the version number to the highest possible allowed by the structure, then in theory no player will bother importing anymore files as it will always think it has the latest.
|
14th January 2007, 13:47 | #757 | Link | |
Guest
Posts: n/a
|
Quote:
|
|
14th January 2007, 13:53 | #758 | Link | |
Old fart
Join Date: Oct 2001
Posts: 3,589
|
Quote:
What could it be? Different Key? Tried it twice, once with the new modified version. Any thoughts as to what else to try? Mark
__________________
Oh no Mr. Bill! |
|
14th January 2007, 15:09 | #760 | Link |
Registered User
Join Date: Jan 2007
Posts: 1
|
Revocation facts from: http://www.aacsla.com/specifications...ommon_0.91.pdf
MKB has three methods of revocation, two specifically for PC's with separate devices/playback software and is described in detail in Section 4 of above document. Summary here: 1. Device Revocation List (DRL): Each device (i.e. XBOX360 HDDVD Drive) has an id attached to it in a record that has been signed by AACS_LA private key (Section 4.1) and is verified as having not been modified by the Host using the AACS_LA public key. This is versioned inside the MKB which is also signed by the AACS_LA private key (Section 3.2.5.8) and checked it is not modified before use. This pretty much discounts modifying the device id or setting the version of the DRL to it's maximum. (unless we have the AACS_LA private key which is nearly impossible to get/brute force) 2. Host Revocation List (HRL): This is the software running on the pc i.e. (PowerDVD, WinDVD) has it's own id again in a record that has been signed by the AACS_LA private key (Section 4.2) and prevents the same kind of attacks as per the DRL above. 3. Key revocation via Subset-Difference Tree or NNL-Tree: (Seciton 3) This is used both to calculate the Volume Key used by BackupHDDVD and to revoke DEVICE KEYS. Again this is part of the AACS_LA signed MKB and can't be altered. The interesting part of this is that each device calculates the same Volume Key for each disk with the same MKB (this will usually be the same for each "title" in a particular batch as has been proved). Hope that dispels some of the incorrect information/questions being posted. |
Thread Tools | Search this Thread |
Display Modes | |
|
|