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. |
|
|
Thread Tools | Search this Thread | Display Modes |
12th March 2007, 04:25 | #23 | Link |
Resident DRM Hater
Join Date: Oct 2006
Location: International waters
Posts: 242
|
Excellent work, I can't test it myself but it looks great. Just thinking though you should add an ASCII view of the volume ID, as those seem to be ASCII fairly often.
__________________
Because Moogles pwn. |
12th March 2007, 13:20 | #24 | Link |
Registered User
Join Date: Oct 2002
Posts: 65
|
GREAT WORK!!!! I have tested on SEVERAL BLu Ray discs and it is working on all of them (at least producing what appears to be working keys). I can't confirm the keys are valid without title hash (unless I'm missing something).
|
12th March 2007, 17:47 | #25 | Link | |
Registered User
Join Date: Feb 2003
Posts: 41
|
Quote:
If this is a program revealing all AACS Key's needed to decrypt, does that mean it is hidden somewhere in the output? Thanks, great job!
__________________
___ |
|
12th March 2007, 18:09 | #26 | Link |
Registered User
Join Date: Jan 2007
Location: Internet
Posts: 378
|
The title hash is the SHA-1 hash value from the file AACS\CPSUnit00001.cci off the disc. There are many programs which can calculate a SHA-1 hash, e.g. HexWorkshop or WinHEX. Btw., this identifier is not very well chosen, there are already titles which have the same title hash. This is because this file does not contain information that is unique per title, it contains Copyright Control Information. If two discs have the same number of titles and use the same copy-rights (things like Image Constraint Token and so on) they will produce the same title hash.
Therefor, when BluRay support is included into DumpHD it will use the SHA-1 hash of the file AACS\Unit_Key_RO.inf as title hash. |
12th March 2007, 18:51 | #27 | Link | |
Registered User
Join Date: Sep 2006
Posts: 390
|
Quote:
Theoretically the Unit Key files could be the same for some discs aswell. But I don't know if they would actually do that (different vuks with the same unit key file lead to different unit keys, so they could do this since there is no tkfmac). Anyway. If you're going to do this then I will do the same with my program aacskeys: hashing the title key file for HD DVDs and hashing the Unit Key file for blu-ray discs. So our programs will be compatible that way. What should we do if there are multiple title key file btw? (for hd dvd only I believe) Is there a specific file format you're going to use? Or plain pipe separated? I thought about using ";" or "//" or something as comment markers at the beginning of each comment line (at the beginning of the file). Maybe also column names. I like to keep it really basic and simple though . Regards, arnezami Last edited by arnezami; 12th March 2007 at 18:56. |
|
12th March 2007, 21:20 | #28 | Link |
Registered User
Join Date: Feb 2007
Posts: 123
|
First of all, fantastic work to all that have contributed to make this program happen =)
Regaring the source, I can understand that you want to wait a while before releasing it. But the problem is, if Doom9 gets closed in the meantime, the source is not released =( So what if you made a rar/gpg encrypted archive of the source available, and when you feel it is ready we get the passphrase? =) The advantage is that if Doom9 should get closed, it is easier to make a passphrase slip, so someone can make a Slashdot story, that THE passphrase have slipped and it is ####, rather than having to release the soruce. =) Another advantage is, that if you tell the passphrase to a few trusted secret people, and you should go silent, the passphrase is still out there, and you haven't released it after you have gone silent. Someone else have, and it could be anybody. Who knows who you can trust these days? =) Ps. It would be fun if the passphrase was 4737676058d7029452514f0ab186dc4cca8c578f . Just of the irony =) Last edited by lightshadow; 12th March 2007 at 21:23. Reason: Added passphrase sugestion |
12th March 2007, 21:44 | #29 | Link | |
Registered User
Join Date: Sep 2006
Posts: 390
|
Quote:
Here is is: source. You need openssl for this to work. This is not an "official" release. This is just for those who want to play around with it. Regards, arnezami Last edited by arnezami; 12th March 2007 at 22:05. |
|
13th March 2007, 07:10 | #32 | Link |
Registered User
Join Date: Feb 2007
Posts: 2
|
I tried it on a bluray iso copied from PS3. I got the processing key, which is the one we all know. I also got the media key but then the program aborted with message saying "all AGIDs in use".
Then I tried it on the PS3 linux with the original movie for the above ISO, then I got the "permission denied" message. So I guess it is no go if I don't have a BD drive connected to my PC, right? Sorry for the newb question. |
13th March 2007, 07:56 | #33 | Link |
Registered User
Join Date: Sep 2006
Posts: 390
|
Could somebody try to compile this on linux (PS3 or PC).
aacskeys multi platform source. (linux + windows) This version should compile both on windows as on linux. But I haven't tested it yet on linux. Please keep me informed of any problems and/or solutions. The instructions are almost the the same as for aacsauth: Code:
INSTALL You need openssl 0.9.8 Compile with gcc -o aacskeys -lcrypto ioctl.c ecdsa.c mmc.c aes.c aacsauth.c There may be some warnings. But hopefully it compiles for linux now (not tested yet). USAGE Type something like ./aacskeys /dev/scd0 v /dev/scd0 is the device file of your drive arnezami PS. The PS3 uses a hypervisor which might prevent it from getting the volume id at all. And mounted ISOs can't handle the mmc commands properly. PPS. The old source should't work on linux unless adapted of course . Last edited by arnezami; 13th March 2007 at 08:09. |
13th March 2007, 10:01 | #34 | Link |
Registered User
Join Date: Feb 2007
Posts: 2
|
This one compiles now on linux. Still untested on PS3.
http://www.sendspace.com/file/x9nmjq |
13th March 2007, 11:09 | #35 | Link | |||
Registered User
Join Date: Jan 2007
Location: Internet
Posts: 378
|
Quote:
Quote:
Quote:
|
|||
13th March 2007, 19:28 | #36 | Link | |
Registered User
Join Date: Sep 2006
Posts: 390
|
Quote:
Also you added this to the aacskeys.h: Code:
#if !defined(linux) int send_cmd(drive_handle h, unsigned char *cmd, unsigned char *buf, size_t send, size_t recv); #endif Thanks. People own a PS3 could try to compile it on their PS3 and see what happens... (i'm quite curious) Regards, arnezami |
|
13th March 2007, 19:33 | #37 | Link | ||||
Registered User
Join Date: Sep 2006
Posts: 390
|
Quote:
Quote:
Quote:
Quote:
Regards, arnezami Last edited by arnezami; 13th March 2007 at 19:40. |
||||
13th March 2007, 19:47 | #38 | Link | |
Registered User
Join Date: Mar 2007
Posts: 8
|
Quote:
|
|
13th March 2007, 21:57 | #39 | Link | |
Registered User
Join Date: Feb 2007
Posts: 6
|
Quote:
Code:
INSTALL You need openssl 0.9.8 Compile with gcc -o aacskeys -lcrypto ioctl.c ecdsa.c mmc.c aes.c aacsauth.c There may be some warnings. But hopefully it compiles for linux now (not tested yet). USAGE Type something like ./aacskeys /dev/scd0 v /dev/scd0 is the device file of your drive |
|
13th March 2007, 23:53 | #40 | Link | |
JuSt a PoWer uSEr
Join Date: Mar 2005
Location: None of your Business
Posts: 288
|
here I tried in gentoo, and it compiles,But cannot test no HDDVd or BlUray disk nor drives
Quote:
|
|
|
|