Wrong, they're not litigating over breach of contract. They're seeking legal recourse and damages on the grounds that he violated the Digital Millenium Copyright Act. It has little to do with the TOU.[QUOTE="jedikevin2"]
Because putting up data of reverse engineering has alot of legality to it. If he was charging for something then we would have a issue.. Thats why sony is not even sueing that argument as Geo is legality in the right on that side.. That are trying to dismiss his actions as against the ToU that apparently you authorize by just buying the product because the statement is int he box and if you go online on the platform is authorization.
shinrabanshou
Exemptions for research and reverse engineering exist in the DMCA, but George Hotz does not meet the requirements of these exemptions as far as I'm aware.
Yes, the DMCA goes with this as sony is trying to state they own the software of the OS. Problem is, by buying the ps3, a person is has the right to do with they please. Thats where the ToU comes in where it states by aggreeing to it, they void any measure of ownership of the software inside of the ps3 nor are you allowing ability to legally mess with the hwardware inside the machine. They both go together. The DMCA is more of a mute point in this regard and only is applied if the ToU written on the manual and what you aggree to in the software when access the PSN is met. If you fail the ToU, mess with software, you fail the DMCA. If you do not fail the ToU, do what you please and discuss said exploits then that is where the grey area exist. That is what i'm getting right now on all of this.
Ps... If you read Geohots lawyers lawsuit response to the court, they specifically discuss, Sony assertion that Geo failed the ToU, that the violation should be withount California jurisdiction (GEO is from New york), the Geo through use of a paypall account made money in the form of ads on youtube, twitter, etc, that the code was already out in the public before Geo actually posted his release of the code, etc etc..
Log in to comment