Picking the lock involves trespassing your property. Breaking the DRM is illegal regardless of if it's trespassing on anyone's property.
> How can bypassing DRM even be illegal?
Same way anything else can be illegal, they made a law saying so.
>a technological measure "effectively controls access to a work" if the measure, in the ordinary course of its operation, requires the application of information, or a process or a treatment, with the authority of the copyright owner, to gain access to the work.
So bypassing trivial DRM is still a crime.
I agree with you on all the other bits, but I'm curious as to why you believe it's unconstitutional. Not trolling here; I don't think I've heard constitutionality arguments against the DMCA, and I'm curious if there's something there.
PS: thanks djb (c.f. Bernstein v USA)
Unfortunately, the Supreme Court's one big proponent against copyright overreach is leaving the court soon.
> If someone owns their hardware then you can do any hardware or software modifications you want to it.
In practice, this isn't something you'd get in trouble for. But if you were to distribute tools and how-tos to help others modify their hardware, that's the bit that really gets you in trouble. I believe there's a carve-out for tools that have significant non-infringing uses, but I'm not sure how well that defense usually holds up.
But yeah, overall it's stupid, and disgusting that this has been the law of the land for over two decades now.
Doesn't matter outside of that, the law is poorly written, any means or attempt to break the circumvention is a violation.
That was exactly the case with YouTube's DRM (video URL is encrypted with a key that is embedded in the javascript for the web page) and was the basis for the takedown against youtube-dl. I am not sure what the court would rule, because in that case everyone from GitHub to Google told the RIAA to pound sand and people didn't get sued.
Any damages would be eaten up by lawyer's fees. The legal fees are (arguably?) worth it to protect a whole system's games from being freely available but the lawsuit itself would not be profitable.
Sklyarov was taken to court, and ~I believe is still in jail~, for bypassing Adobe's use of the amazingly secure ROT13 cypher.
EDIT: Charges were dropped a year later, because of the insanity of charging someone for using such an insecure mechanism. But only after both the EFF and Adobe came out in support of Sklyarov.
[0] https://www.zdnet.com/article/dimitry-sklyarov-enemy-or-frie...
In the early days of Switch hacking, there were mostly people just poking and prodding at different parts of the console to see if it would spit out interesting stuff. Fairly rudimentary stuff, like checking for secret Amiibo with custom NFC tags, hacking together Joycon drivers and even opening the device to play with the exposed hardware: all of it perfectly legal. Eventually though, someone found the secret switch on the bookshelf (shorting out one of the physical controller connector pins if you're curious), and the community was off to the races to design a custom bootloader/firmware like they did on the 3DS and Wii.
This is where the problems start, as I'm sure most people here would know. Messing with software is a dangerous thing (legally speaking), and so effectively 2 camps were formed:
- Team Xecuter, a close-knit circle of devs who intended to hack the Switch come Hell or hard-modding. They had no stipulations against using leaked code, directly profiting off their customerbase or inflaming their community, when it came down to it.
- Team Atmosphère, an open-source project that went with the "slow and steady" approach, attempting to find an ethical softmodding solution that could easily be applied to any Switch without fear of legal repercussion.
Both of these teams would fight each other viciously over the course of 2 or 3 years. Team Xecuter was first to figure out game piracy, but Atmosphere had a working warmboot before Xecuter did. Atmosphere was able to install games locally before Xecuter could, but Xecuter figured out booting from attached storage before Atmosphere did. The groups traded blows like this continually until, like Napoleon looking out on the Mediterranean, there were no more features to conquer. Xecuter had an easy-to-install commercial hardmod that was almost exclusively designed for piracy, while Atmosphere had polished off a more difficult but rewarding softmod, with emulation and homebrew capabilities (and eventually piracy, too).
So, what was Team Xecuter's crime? Putting the signing keys in the hardmods they sent out. With every successive Switch firmware update, Nintendo would issue a new list of attestation keys that came with each game purchase. To allow unsigned games to be booted, TX packed in these keys (and offered them on a monthly basis afterwards to hardmod owners), which really sent Nintendo off, leading to arrests like the one mentioned here. Atmosphere remains thankfully untouched today, and even though the odds looked stacked against them, they have delivered the most polished Nintendo Switch modding experience you could ask for. It's quite wonderful stuff, especially if you've ever wondered "how would this Python script run on Switch...?"
...oh, and the Switch modding community was absolutely insane for those few competitive years. There were a few other noteworthy community villains like Blawar, but that's a story for a different time.
All of this could be seen from miles away from the beginning though. Thoughtfully-built software tends to live longer than hastily made products, Atmosphère had already won the second TX decided to step in the ring.
> Nintendo have had a conflicted stance about community projects over the years. From threatening UltraHLE (early Nintendo 64 emulator) developers back in the late 90s to largely ignoring the Wii exploits and homebrew scene in the mid-to-late 2000s to attempting to hire private investigators to identify and implicate 3DS homebrew developers in 'illegal' activities.
Ultimately I think if Xecuter did not have their product so closely intertwined with enablement of piracy and distribution of copyrighted content it would leave Nintendo less legal ammo to use against them and potentially make it not worth pursuing.
Important to note the RCM exploit only works for the first revision of Switch units. This does not justify other potential crimes Xecuter may have done but certain previous mod-chips for certain previous consoles have been open-source in a clean-room design not including copyrighted content by the original vendors thus potentially removing issues of copyright infringement. Sad the Switch scene could not be the same.
Had they not shipped code-signing patches and advertised this as a way to private games, I'm curious if the defense would have been easier. What'd they get him on -- the DMCA?
"Conspiracy to Circumvent Technological Measures and to Traffic in Circumvention Devices"
Is this a DMCA violation for using modchips to defeat an IP protection scheme ?
I am not up to date on the current jurisprudence here - if I clean-sheet reverse engineer (Nintendo hardware) is it considered illegal to create and market modchips based on that ?
Or did they have proprietary code/firmware/loaders copied into them ?