• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

AACS (hddvd and blu-ray) cracked

Originally posted by: Anubis
Originally posted by: Goosemaster
the key can be reset invalidating all of this.


move along people.



This new method bypasses this step and allows anyone to extract the data without first requiring the volume key."

ummmm

IIRC some guy on /. said it could be invalidated.


Hey, I'm not complaining. Just saying that I heard otherwise..that's all.
 
Yeah, it seems it can be invalidated, but it looks like it's a much more direct way of decrypting the discs. At the rate at which they're being decrypted and posted on the net, it won't really matter if they invalidate the key.
 
The thing is, the way the key was broken this time is that WinDVD/PowerDVD stored the volume key in memory for a time and then wiped it afterwards, leaving obvious traces of zeroes. Now that such a software exists (that stores the volume key in memory) no matter how they change it, it'll still be accessible through that same version of Win/PowerDVD.
They can't make too radical of a change because it'll make currently owned HDDVD/BR players obsolete, which will create large problems.
Essentially, the MPAA got kicked in the nuts. They can respond in some ways , but I'm against DRM in principle so I hope they don't. Also, anything they do will get cracked. It's h4x0rs with principle that get it done.
 
Originally posted by: Goosemaster
the key can be reset invalidating all of this.


move along people.

From a Slashdot post:

The MPAA can revoke the processing key, but quoting from the forum:

Some of you are missing the true meaning of this compromise. If they revoke this processing key, we just take a player compatible with a new processing key, put in one of the titles that's already cracked, and go around in memory looking for the known key. We find it, insert a new title, look in the same place and we have a new processing key.

Essentially, it becomes a known-plaintext attack.
 
Originally posted by: Astaroth33
Originally posted by: Goosemaster
the key can be reset invalidating all of this.


move along people.

From a Slashdot post:

The MPAA can revoke the processing key, but quoting from the forum:

Some of you are missing the true meaning of this compromise. If they revoke this processing key, we just take a player compatible with a new processing key, put in one of the titles that's already cracked, and go around in memory looking for the known key. We find it, insert a new title, look in the same place and we have a new processing key.

Essentially, it becomes a known-plaintext attack.

I stand corrected.



<---was reading /. on his phone in the library when he was supposed to be studying😱
 
I really think the big companies are wasting money on fighting the people who crack this stuff buy coming up with the challenges.


What they need to do is figure a way to make what the crackers do not worth them doing. At the same time they need to keep some profit to keep their shareholders happy.


I doubt this will ever happen though....
 

Actually read it and you'll see why it's different.

The previous posts refer to cracked HD/Blu-ray programs, where you could get the key for the disc from a fault in the program. AACS itself wasn't cracked, the programs (winDVD and/or powerDVD) were. The gist of it is people can copy discs using a hole in commercially available software. The MPAA just has to revoke the keys used by those programs, and use new keys on new discs, patch the holes in the programs, and everything's back to square 1.

With this new crack people now know where to look in memory for any key they like. The implementation itself has now been cracked, and revoking keys will only slow down the decryption process by a few minutes. This is a hole they apparently won't be able to patch without major changes causing huge inconveniences to, well, everyone.
 
But how long would it take? I think I read somewhere that the original method took like 50 hours to encode.

Cheers,
Aquaman
 
Back
Top