Is Microsoft Using RIAA Legal Tactics?
Nom du Keyboard writes, "CNET reports, 'Microsoft has filed a federal lawsuit against an alleged hacker who broke through its copy protection technology, charging that the mystery developer somehow gained access to its copyrighted source code.' Looks to me like since they can't figure out how else he's doing it, they'll sue on this pretense and go fishing for the actual method through the legal system. They clearly have no proof yet that any theft of source code actually happened. This smacks of the RIAA tactics of sue first, then force you to hand over your hard drive to incriminate yourself. Isn't this something the courts should be putting a stop to at the first motion for dismissal?" Viodentia has denied using any proprietary source code, according to CNET.
because windows is so complex not even MS can figure it out. they dont think this dude could.
Anyone want to explain the logic behind that statement?
MS gives out the SDK
The SDK contains source code that is "not easily accessible"
Someone accesses the source code.
MS cries foul!
[Fuck Beta]
o0t!
The 5th Amendment would not generally apply, since it's a copyright infringement claim and thus not a criminal offense. The 5th Amendment pertains to crimes, not torts. Further, the 5th Amendment is understood to refer to the government compelling you to implicate yourself through testimony, not a third party or through evidence.
That said, the as-of-yet-unchallenged Digital Millennium Copyright Act clearly makes "access" to copyrighted works without a license illegal if they are "digital". Under that law, "access" to "digital" copyrighted works is indeed a crime. In that case, if the government got involved in the prosecution the 5th Amendment may very well apply with regard to whatever testimony you give.
I dunno...there was a slashdot discussion with an argument similar to this. He did not technically crack or break any DRM. The WMP by nature decrypts the file, in order to play it. Now, right after WMP decrypts it...it is a file in memory just like any other file/code, and I don't know of any rules or laws out there that say what you can or cannot do to any bit of data in memory...especially if it is in a decoded, freely readable format. Are you 'forced' to play it through the speakers? What legally keeps you from directing that data to another file, or hell...to the printer if you saw fit?
It seems the legalese people try to argue this kind of crap to the letter of the law. And from what the DMCA seems to rule against is cracking the DRM on a file...but, I see nothing in it saying what you can or cannot do with the data once the DRM has been legally removed.
I think by definition, while yes you may have circumvented the way someone intended you to use the system...you in fact have not circumvented the DRM itself, and I think that is what the DMCA specifically tries to outlaw.
At the very least..like another poster said, couldn't this be defended as a way to allow interoperability with other applications/oses and the like, which DMCA does allow?
Light travels faster than sound. This is why some people appear bright until you hear them speak.........
I found one claim in there particularly interesting:
I wonder...why is that, exactly? Why is Vista such a massive project?
It's a serious question. I mean, it's not like they're building HAL-9000 here. It's an OS. A microcomputer OS. Which really, as far as I can tell, doesn't do a whole lot more than a bunch of other OSes that are on the market already. What does it do that's so much more complex, fundamentally, than what OS X does? Or Linux? Or any number of other OSes? Why, exactly, is it such a freaking huge project?
If the size estimates I'm reading are accurate, at 50 MLOC, Vista is still smaller than OS X at 80 MLOC (comparisons to Linux are tougher because when someone says "Debian has 160 MLOC," it's not clear if that's just the base system or including all the applications or what). Admittedly, OS X borrowed a lot of code from NeXT, but Microsoft has a lot of code they could steal from previous Windows versions and other projects. If they chose not to, then that was a conscious management decision on their part.
If this guy's characterization of Vista development is true, they have more problems than a slipped schedule; they need to be asking why the damn thing has turned into that much of an epic project in the first place. This is not like IBM building the S/360 here; they're not wandering that far off into uncharted, never-before-attempted territory, based on every description of Vista I've ever seen or heard of. Yet they're making it that much of an effort, either by choice or mismanagement.
Vista, Linux, OS X: it does the same thing. Ultimately, they're both ways of managing the filesystem and the computer's hardware resources, and presenting those resources to programs in a standard manner on one end, and presenting a GUI to the user on the other. Sure, they're different ways of doing things, but they're all solutions to the same basic problem. It's even the same hardware resources and architecture that they're supposed to manage -- it's not as though the premise of each is that different.
Frankly if what that article says is true, Vista might have a second, more dubious distinction: the most wasted effort ever spent on a project since the Russians built that expensive lawn ornament.
If this guy did see the source code and was able to reverse engineer it, Microsoft ought to offer him a job. Apparently, they need the help.
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."