Posted by Tim Smith on 01/04/07 17:56

On 2007-01-04, JoeBloe <joebloe@thebarattheendoftheuniverse.org> wrote:
>>This depends on what you mean by "broke". In particular, do you
>>consider a successful brute force attack a break? With its mere 40-bit
>>key length, and weak algorithms, CSS falls fairly quickly to a brute
>>force attack, in about 2^25 steps.
>
>
> Show me where a person wrote an app that took a DVD drive and
> extrapolated a brute force key to use to decode the stream coming off
> the drive.
>
> CITE, you retarded mother fucker! Math doesn't mean jack shit if
> the logistics to actually implement it are too costly for the fucktard
> pirate brute twit to utilize.

The code is in libdvdcss. Set the DVDCSS_METHOD environment variable to
"disc" and libdvdcss will brute-force the disc key. Set that variable
to "title" it will use an attack on the title key.

Brute force attacks that require about 2^25 steps aren't too costly.
About 5 years ago, it required a fairly high-end PC, because it took
about 64 MB of RAM, but that's trivial now. Timewise, it took about
a day back then, and is much quicker now.

> Show me where it was ever done. DeCSS MPEG-2 DVD datagram encryption

It's done in basically every player that uses libdvdcss. BTW, if you
want to pretend you know something about this subject, you should start
getting the name of the system right. It's "CSS", not "DeCSS". DeCSS
was/is software to break CSS.


> was fine until the keys were released. Even though said keys have been
> released, I never5 saw any subsequent reports of any jerk having
> actually cracked it. I don't care how long the fucking string is,
> dipshit.

It's not surprising that you don't care about the effective key length,
since you apparently know nothing about cryptography.

[Back to original message]