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. |
|
4th March 2007, 00:51 | #1 | Link |
Registered User
Join Date: Feb 2007
Posts: 1
|
PowerDVD private key
Finally I'm allowed to post :-)
It will be revoked because AnyDVD is using it. So here it is... My source http://rapidshare.com/files/18598966...th.tar.gz.html is mad and works on Linux only (but maybe PS3). But the important part is 4737676058d7029452514f0ab186dc4cca8c578f anyway. BTW WinDVD and even AnyDVD is hiding it better than PowerDVD ;-) The point is probably their bignum stuff. Maybe it is a problem of little/big endian, too. |
4th March 2007, 00:55 | #2 | Link | |
Registered User
Join Date: Sep 2006
Posts: 390
|
Quote:
I've really been struggling with WinDVD. The SHA-1 hash and private key simply don't seem to appear in memory (while Hv, Dv, Hn, Dn, Hpub, Dpub, Hsig and Dsig do). The bignum/endian might indeed be throwing me off. Anyway. Great work ! One for the history books I will check/confirm this as soon as I've got time. Last edited by arnezami; 4th March 2007 at 01:18. |
|
4th March 2007, 02:02 | #5 | Link |
Registered User
Join Date: Sep 2006
Posts: 390
|
Ok. I can confirm that the public key in your program corresponds to the private key you gave (using my own proggy). Its probably from PowerDVD 7.x or something because it is different from the 6.5 version (the only one I have atm). I haven't got your source working yet on windows but hopefully tomorrow...
Can anybody sniff a PowerDVD 7.x and ascii search (not hex search) for "00000000: 00 72 00 00". There are two of those. The first one should be the one with "02 00 00 5c ff ff 00 00" in it. (careful: do NOT post the other one!) The Hcert part should look like this: Code:
02 00 00 5c ff ff 00 00 00 0c 00 00 6e 3d eb 67 9b 9a 16 ad fa a8 e3 08 78 76 7b a6 eb 2a 9b 41 53 85 ad 11 81 b4 44 6c 31 e9 a5 dd 2a b8 08 b3 64 ff 15 88 5b ac 49 09 64 31 8c 9b f8 02 9f cf 76 f6 88 a5 4f bd a0 3f 6d 93 32 ef 04 e5 a6 13 12 da 85 88 0a 4d 9c bb 79 d8 60 2e Oooh this is so cool Last edited by arnezami; 4th March 2007 at 02:14. |
4th March 2007, 09:56 | #10 | Link |
Registered User
Join Date: Sep 2006
Posts: 390
|
Well that proggy is beyond chaotic . But I think I will extend jx6bpm's program so it will produce all aacs keys and ids:
@jx6bpm: can we assume your source is public domain? Last edited by arnezami; 4th March 2007 at 10:08. |
4th March 2007, 20:45 | #12 | Link | |
I swallow bugs!
Join Date: Jan 2007
Location: Whitehouse corner Office
Posts: 49
|
Quote:
Now what charity do you guy's want me to send my $35.00 to..(my cost to purchase one HD DVD here) ie Cancer Research ...Diabeties Research...Jerry Lewis fund... Anyone here who has helped in the diagnostic of this DRM disease can pm me their charity of choice. PS.. I have sending a check to THE Tom Baker Cancer Centre here for the original work (muslix64) and now I will send in $35.00 to the Canadian Heart and Stroke fondation, for (jx6bpm) and an additioal $35.00 to the Canadain Diabeties Fondation for (arnezami) work. Disclaimer: These donation are expression given by me without any prior conversion to any of the above parties. Again great work. Last edited by frogman; 5th March 2007 at 01:13. Reason: typo |
|
4th March 2007, 18:10 | #13 | Link |
Registered User
Join Date: Feb 2007
Posts: 6
|
Searched it on PowerDVD 7.1 HD... with V for Vendetta playing, looks similar to the one you posted arnezami...
I just thought I'd post it just so you can see the difference (if there is any) Code:
0200005CFFFF0000000C00006E3DEB67 9B9A16ADFAA8E30878767BA6EB2A9B41 5385AD1181B4446C31E9A5DD2AB808B3 64FF15885BAC490964318C9BF8029FCF 76F688A54FBDA03F6D9332EF04E5A613 12DA85880A4D9CBB79D8602E |
4th March 2007, 18:43 | #14 | Link | |
Registered User
Join Date: Sep 2006
Posts: 390
|
Quote:
|
|
5th March 2007, 01:35 | #16 | Link |
JuSt a PoWer uSEr
Join Date: Mar 2005
Location: None of your Business
Posts: 288
|
Yes, but only for newer disks. Old disk will still play fine.
and we will have to find a new key for the newer disks
__________________
Birthdays are good. Statistics show that the people who have the most live the longest. Last edited by dirio49; 5th March 2007 at 01:44. |
5th March 2007, 01:48 | #17 | Link | |
Registered User
Join Date: Jan 2007
Posts: 11
|
Quote:
That is, if the player has to do something to tell the drive about the revocation. If the drive detects it by itself, then attempting to play a newer disc will result in the drive refusing to work with the older host private key. Assuming that the player does need to tell the drive about the revocation, then an older host private key could theoretically be used in a non-revocation-compliant player even on newer discs and then only a newer device key or processing key would be needed. However, I'm sure AACS LA would not have left such a big hole open, meaning that the host key revocation is probably an automatic thing on the drives (for example, if the drive checks the host signature against something on the disc). Of course, older discs will still be able to be decrypted, as the volume unique keys or volume IDs for the discs will have likely already been published. Last edited by ShadowFlare; 5th March 2007 at 01:54. |
|
5th March 2007, 06:20 | #18 | Link |
Registered User
Join Date: Sep 2006
Posts: 390
|
I believe this was already clear but I will explain it very clearly now:
When a new disc is inserted the drive is told not to give Volume IDs to the Software Player with the now found Private Key. It will remember this in its permanent memory. This means that from that moment: old and new discs will not work anymore (because of the missing Volume ID). Until we find a new Private Key that is. Of course if you store (or we let the program automatically store) all VUKs for all old discs you inserted before putting in the new disc in the drive these old discs can still be decrypted based on the VUKs. The reason: VUKs are not revokable (as muslix64 already pointed out). Thats why we always have to keep collecting VUKs. This is just an easier way and a program can do it automatically. Last edited by arnezami; 8th March 2007 at 17:40. |
5th March 2007, 11:44 | #19 | Link | |
Registered User
Join Date: Feb 2007
Posts: 86
|
Quote:
Then how will you explain this: http://forum.slysoft.com/showthread....5247#post15247 Slysoft developers say AnyDVD HD will not be affected by this scenario... |
|
5th March 2007, 01:41 | #20 | Link | |
Dwight Schrute's homeboy
Join Date: Jan 2007
Location: The Office
Posts: 136
|
Quote:
It will only stop working for the new disc which has that "device key" revoked. But it will still work for the 100s of titles already out. |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|