>It took almost two years to crack CSS, and that was only because Xing didn't encrypt their keys
Oh really? I suggest you head over to Fravia and fresh up your reverse engineering skills. The fact that Xing failed to protect their keys probably speeded up the development of DeCSS by one hour or so. If they had protected them, the decryption code for the keys would also have been included in the player. You would then locate that code and use it to decrypt the keys, or you would get the keys after the player had decrypted them. It could have been any player that was reverse engineered.
On your question what happened to Xing, well, they got their key revoked so I guess their support division is getting a lot of questions on why someone's brand new movie doesn't work with their player.
Now, how do you know it took 2 years to crack CSS? Don't you know the saying, assumption is the mother of all fuckups?:) There were pirated DVDs (Hollywood movies) on the street in Russia back in Summer99 which were not encrypted (and the US eq. of these being encrypted ofcourse). They hadn't been decrypted for piracy purposes (because you don't need to), but because they had replaced english audio and subtitling with russian.
And regarding SDMI, it sure will get cracked. There will never be a Free Software SDMI player. That itself will speed up the process of SDMI being cracked. And there's always the trick of having a soundcard driver that saves the audio stream to the harddrive.
I recently changed from BIND (the Buggy Internet Name Daemon) to D. J. Bernstein's DJBDNS. It's a very modular, robust and not to mention secure replacement for BIND. He's got a security guarantee as well. He offers $500 to the first person who reports a verifiable security hole.
So instead of worrying about the next serious security hole in BIND, replace it with DJBDNS and make your server a lot more secure.
when trying to make it easier to use (Microsoft all over). I'm fairly confident that this can't be caused by a normal SMS-msg with "normal" text (unless those Nokia engineers pulled it off -again-). Nokia phones can be configured using SMS-messages. Take Nokia WAP phones for example. They can be configured for WAP operation by receiveing an SMS message from your operator. Non-WAP Nokia phones also have similar functionality. Sending a malformed "config" msg might be what is causing this. Anyway, big deal. Nokia is a "designer" phone. Nice looks. Geeks in Scandinavia go for Ericsson (yes, I know they've fucked up in the past, but at least not as bad as Nokia this time:)
From the divx.st site: "DVD-Quality". Let's get one thing straight: DivX does not give you DVD-quality, and IMHO it doesn't even come close to DVDs. If you're a movie enthusiast, you'll know what I'm talking about.
And yes, MPEG4 is a standard. Microsoft has implemented that standard. Their implementation is not called DivX. DivX (which has nothing to do with Circuit City) is Microsoft's MPEG4 codec which has been modified to allow the use of MP3 and WMA audio. (No, it's not blessed by MS:)
As you probably understand, I don't like DivX that much. It gives you great quality at a small filesize, but it's nowhere near DVD-quality.
I don't understand why anyone would spend time working on that port anyway. Go contribute to something like OVD ("Open" counterpart to DVD) instead. Checkout linuxvideo.org for more info.
Slashdot Mirror
>It took almost two years to crack CSS, and that was only because Xing didn't encrypt their keys
:) There were pirated DVDs (Hollywood movies) on the street in Russia back in Summer99 which were not encrypted (and the US eq. of these being encrypted ofcourse). They hadn't been decrypted for piracy purposes (because you don't need to), but because they had replaced english audio and subtitling with russian.
Oh really? I suggest you head over to Fravia and fresh up your reverse engineering skills. The fact that Xing failed to protect their keys probably speeded up the development of DeCSS by one hour or so. If they had protected them, the decryption code for the keys would also have been included in the player. You would then locate that code and use it to decrypt the keys, or you would get the keys after the player had decrypted them. It could have been any player that was reverse engineered.
On your question what happened to Xing, well, they got their key revoked so I guess their support division is getting a lot of questions on why someone's brand new movie doesn't work with their player.
Now, how do you know it took 2 years to crack CSS? Don't you know the saying, assumption is the mother of all fuckups?
And regarding SDMI, it sure will get cracked. There will never be a Free Software SDMI player. That itself will speed up the process of SDMI being cracked. And there's always the trick of having a soundcard driver that saves the audio stream to the harddrive.
I recently changed from BIND (the Buggy Internet Name Daemon) to D. J. Bernstein's DJBDNS. It's a very modular, robust and not to mention secure replacement for BIND. He's got a security guarantee as well. He offers $500 to the first person who reports a verifiable security hole.
/usr/ports/net/djbdns; make; make install
So instead of worrying about the next serious security hole in BIND, replace it with DJBDNS and make your server a lot more secure.
Homepage: http://cr.yp.to/djbdns.html
For OpenBSD users: cd
when trying to make it easier to use (Microsoft all over). I'm fairly confident that this can't be caused by a normal SMS-msg with "normal" text (unless those Nokia engineers pulled it off -again-). Nokia phones can be configured using SMS-messages. Take Nokia WAP phones for example. They can be configured for WAP operation by receiveing an SMS message from your operator. Non-WAP Nokia phones also have similar functionality. Sending a malformed "config" msg might be what is causing this. Anyway, big deal. Nokia is a "designer" phone. Nice looks. Geeks in Scandinavia go for Ericsson (yes, I know they've fucked up in the past, but at least not as bad as Nokia this time :)
From the divx.st site: "DVD-Quality". Let's get one thing straight: DivX does not give you DVD-quality, and IMHO it doesn't even come close to DVDs. If you're a movie enthusiast, you'll know what I'm talking about.
:)
And yes, MPEG4 is a standard. Microsoft has implemented that standard. Their implementation is not called DivX. DivX (which has nothing to do with Circuit City) is Microsoft's MPEG4 codec which has been modified to allow the use of MP3 and WMA audio. (No, it's not blessed by MS
As you probably understand, I don't like DivX that much. It gives you great quality at a small filesize, but it's nowhere near DVD-quality.
I don't understand why anyone would spend time working on that port anyway. Go contribute to something like OVD ("Open" counterpart to DVD) instead. Checkout linuxvideo.org for more info.
> Don't be so sure
;-)
Read through the Judge's opinion again, and you'll notice that he states that linking to the material is still allowed
So, link (& mirror outside CA and NY) all you want:
http://mmadb.no/jlj
That's right...
;)
Feel free to link to http://mmadb.no/jlj
It's in Norway and it won't go down