AACS Keys - A program revealing all AACS Keys needed to decrypt (HD DVD and Blu-ray)

[setarip_old]

@ttwater

Hi!

Yes, AnyDvd works well, but I want to achieve the same function without AnyDvd.

Presently, MakeMKV can decrypt any BluRay disc, including the latest BD+...

[ttwater]

Originally Posted by setarip_old

@ttwater

Hi!Presently, MakeMKV can decrypt any BluRay disc, including the latest BD+...

sad message.

I've tried all the functions the MakeMKV have, but it couldn't decrypt my iso too.

i know few about blu-ray now, i think i need to learn more, i will be back.


thanks setarip_old and Supan.

[setarip_old]

@ttwater

I've tried all the functions the MakeMKV have, but it couldn't decrypt my iso too.

1) As I said, it certainly should be able to decrypt both your original BluRay disc and the .ISO image file you created from it.

2) Have you mounted and played the .ISO image file you created on your PC? If not, you may not have created a valid .ISO image file.

[ttwater]

Originally Posted by setarip_old

@ttwater1) As I said, it certainly should be able to decrypt both your original BluRay disc and the .ISO image file you created from it.

2) Have you mounted and played the .ISO image file you created on your PC? If not, you may not have created a valid .ISO image file.

it could played with anydvd's help, powerdvd couldn't. i think my .iso image lossed some data from the original bluray disk, anydvd have a database contained the lossed data, so anydvd could decrypt.(as Supan said)

to Supan:
is it right?

[Guest]

[bump after edit - thread re-opened after erroneously closed - offending rule 6 post has been removed]

[popop]

To my knowledge, all the ISOs no matter from which application you use to create it will NOT work without the help of decrypter like AnyDVD HD due to the AACS protection. In fact the created ISOs don't contain or contain wrong information/keys, so the correct normal procedure of decryption is not possible.

I've tried ImgBurn, AnyDVD HD (with protection not removed) and Alcohol 120% to create the ISO but all are the same.

[dk75]

I've created iso by Linux "dd" command (at PS3) and AnyDVDHD removed protection from it.

[kabelbrand]

Can someone give me a hint how the VUKs for mkb 12,14,15,16 titles seen on the "Post Blu-ray Volume Unique Keys here" thread could have been discovered?
I am searching the forum and internet for a few days now, had a brief look at MakeMKV but failed to find any information.

Thank you!

[EDIT] A forum member pointed out to me that this information is not ready for public release yet. Anyway, I hope there will be new processing keys for AACS Keys some day.

[646C799C]

Originally Posted by kabelbrand

Anyway, I hope there will be new processing keys for AACS Keys some day.

While I certainly share your hope, unfortunately I wouldn't be completely surprised if there aren't anymore unrevoked processing keys released for direct use with aacskeys, since it's gotten hard enough to find them, and once they're found and posted they're often revoked quickly. (Most software player exes are now corrupted with Themida, some even loading plugins that decompress and execute more Themida code in memory in an apparent attempt to slow down hackers, while executing a million unnecessary instructions, wasting power and reducing your system performance. Also, because the processing keys aren't used to decode video directly they may never even be entirely exposed where XORs are used.) And, although it would be nice if authors of commercial decryption software would release their revoked keys, it's not exactly surprising for them to consider this a potential loss of customers, since people who pay for their software don't need VUKs anymore (even if they might be more convenient for users who don't run Windows.) Fortunately, direct access to processing keys isn't necessary to obtain VUKs (I don't have one for MKB14, and that hasn't stopped me...)

Originally Posted by kabelbrand

Can someone give me a hint how the VUKs for mkb 12,14,15,16 titles seen on the "Post Blu-ray Volume Unique Keys here" thread could have been discovered?

Here's a couple (possibly related):
1.When I got the "Could not find a processing key" message the first things I thought were: Exactly what does the processing key do, how does aacskeys know it can't find one, and is there any way to avoid or replace using it directly...
2.Is there anything related to VUK generation recognizable when decrypted? Most systems that know when you supplied an incorrect password are checking for some data, CRC, etc that's only present when decrypted correctly, and "password recovery" programs frequently look for this as well. (If you are able to directly monitor any player, try taking an older Bluray decryptable directly with aacskeys and use it with the player, searching for that (known) key, then comparing with your newer disc. Think dumpvid for VUKs...)

Originally Posted by kabelbrand

A forum member pointed out to me that this information is not ready for public release yet.

While processing keys are unique to a particular licensed player, title/volume keys are not, meaning one advantage of posting only these keys is that the player used to obtain them cannot be determined, and following the results from posting of processing keys where companies are putting glue on PCBs for hardware players and using obfuscating VMs for software, I hope the concern that posting player specific information would cause that player to be updated to make this more difficult is understandable. (Also, I would personally be concerned that if I posted anything that automated key discovery, it could end up helping p2p premieres.)
Finally, this post wouldn't be complete without a new VUK, so here's another MKB16 title:
2675EE2C3F2C093FE770341D1A8242872F3FDF9D = The Hurt Locker (US) | D | 2009-10-23 | M | D30E33F2B7960BA37AC69648FAD4CBA5 | I | FCFBCE5D415DC54BEF03BAB4BAADFDB9 | V | BF106B09A71E8F56B67FA7B90AE2C732
Have Fun!

[jimrip]

Hi

My first ever post so please be gentle. I must stress I am a newbie to using terminal commands but I am getting there slowly with the help of this forum and others.

First off, I have been creating .iso of my blu-ray discs using ubuntu on my PS3 and transferring to an external harddrive. I have then been ripping the .iso using makemkv or dumphd on Mac OS X Snow Leopard. As long as the VUK for my particular disc is in the keydb.config everything is working fine.

However I would like to be able to get the VUK for myself

So my questions are –

Can I use aacskeys on Mac OS X Snow Leopard to obtain the VUK from an .iso created on ubuntu on my PS3?

Can I use aacskeys on my PS3 to obtain the VUK?. The link to download a linux binary for PS3 says its unavailable


Thanks, any guidance is very much appreciated

[880]

No, because the ISO does not have the Volume ID (necessary for the VUK), and the PS3 doesn't allow low-level access to the Blu-ray drive (so you can't get the Volume ID there). The program AnyDVD HD (not free) has most keys built in, so you could use that to rip ISOs.

By the way, Sony is removing the Linux feature from PS3s soon, so beware.

[jimrip]

Thanks for the swift reply. I guess I will have to wait for the keydb to be updated before I can rip my Cars blu-ray. Cars is in the database but its not working.

Thanks again

[setarip_old]

@jimrip

Hi!

If you're going to be doing this on an ongoing basis, you really should consider getting a BluRay reader (or burner) for your Mac. You would then be able to immediately make decrypted full disc copies of your original BluRay discs, using EITHER "MakeMKV", "DVDFab Passkey", or "AnyDVDHD".

[bob-flash]

Without the new Certification, new player Private key, and the new Processing key, aacskeys must be going to die now...
while open source means open the key too, when the key is opened, it's quite easy to revoke...so the mouse and cat game never ends.
If we can use some source code obfuscation skills to make the key not easily be viewed, but still can be compiled with C compiler.

This may get a balance between open source & key revocation.

[pynux]

maybe make a close source only for the part have Processing Key
the rest can be opensource

new HostKeyCerificate :

5F63596894AB301089FCB1FDC51DE71E09C911AE
0200005CFFFF0000272B000003526E93CD01A98D92D0F8FF590767C3388D202B4799B09BEF67E1851E450E2D673C52A12A299CA777E7FA9F8AC88F4A9BF07436D8BB0400FB86AAD60E5EADB5DD69DDE2CB9E109A8212E06F963C4FF9

[dirio49]

I think that could be possible,
But I wonder what it would achieve, protect the key temporarily.
because any hacker could if wanted get the key, by reversing the closed app.

[KenD00]

That idea with the closed part isn't quite good for a couple of reasons. At first it violates the open source idea thats behind this program. Second, the hiding of the key has to be VERY good, if every script kiddy can get it its pretty useless. And of course this has to work on at least 3 different OS, so the effort to realize just this little, non-productive feature, is at least a double digit factor higher than the effort to realize the whole functionality of the program .

And third, and thats the most important point imho, it's almost useless. The AACSLA revokes ALL Device Keys on a regular basis, so no matter how good we hide our stuff, it WILL get revoked. The only benefit of the hiding would be that they MAYBE can't figure out from where we got that key (they can still do black box tests against the program and derive this way where the key comes from) so that they can't point with their fingers on that manufacturer.

Anyway, thanks for the new Certificate, too bad that its not that helpful without recent Processing Keys, but well, better than nothing. Honestly, i haven't worked on aacskeys for a long time now, i have a slightly better version here than the last release but never bothered to make it public because the benefits are quite small. Without recent Processing Keys it doesn't help that much that BDAV's should be decrypted correctly now and that finally it doesn't crash on Mac OSX anymore .

[bob-flash]

Originally Posted by pynux

maybe make a close source only for the part have Processing Key
the rest can be opensource

new HostKeyCerificate :

5F63596894AB301089FCB1FDC51DE71E09C911AE
0200005CFFFF0000272B000003526E93CD01A98D92D0F8FF590767C3388D202B4799B09BEF67E1851E450E2D673C52A12A299CA777E7FA9F8AC88F4A9BF07436D8BB0400FB86AAD60E5EADB5DD69DDE2CB9E109A8212E06F963C4FF9

It's not a valid HostKeyCerificate...

I've tried my effort to dump one from DVDFab, but I only get the Certification part, i can't figure out where is the Host Private Key:

0200005CFFFF0000009400000982963083499FEB8630C1CFEDA323D0257EB4B80365EDC85EA29CD67E1A6E42389CE1EE85410F378CA4BBABBBDA4974B0D7D7C614B4B62412A93DF054E52F01201C0E0ED0E22AE6B434D90C5B14E2A2

[KenD00]

Indeed neither the Certificate is valid nor does the Private Key match it. So i took a closer look at it (i know where its from) and it looks like its sort of obfuscated, i have the correct Certificate now but i still haven't got a matching Private Key.

Well, and as the name implies, the Private Key is private, it never leaves the application and should be secured almost as good as the Device Keys.

[pvh1987]

I'm a newbie and I'm very sorry if I ask a stupid question. I have been reading a lot in this thread to find out how to use aacskeys on discs with mkbv greater than 10. I have seen in the volume unique key posting thread, that some people has managed to get keys for discs with v12, v14, v15, v16 and even mkbv17. I see that my "ProcessingDeviceKeysSimple.txt" only contains information up to mkbv10.

Since somebody has managed to get keys from mkbv17 discs - I should be able to do this as well? But how? aacskeys works very well on my older discs released in 2007 and 2008 - all newer discs seems to fail.

As I said, I have read a lot of information in this thread and I still can't figure it out :-(