Numbers can be illegal under the DMCA, but they lack originality to be copyrighted. They fail both the artistic and sweat of the brow tests, as the number will have been randomly generated by a computer.
en.m.wikipedia.org/wiki/Feist_Publications,_Inc.,_v._Rural_Telephone_Service_Co
The DMCA violation affects any method or information. So the code to derive the key at runtime is also a violation.
Last edited by smf,
SciresM is posting that devkitPro forums were hacked and vandalized, and that the only back up is from 2017.
Is this going to significantly set back 7.0 Atmosphere do you think?
https://mobile.twitter.com/SciresM?ref_src=twsrc^google|twcamp^serp|twgr^author
Is this going to significantly set back 7.0 Atmosphere do you think?
https://mobile.twitter.com/SciresM?ref_src=twsrc^google|twcamp^serp|twgr^author
SciresM must have a local copy of DevkitPro so I don't think it will impact atmos, at least there's some undergoing change in ARM tool chain or something.
https://twitter.com/SciresM/status/1092655610489798657
SciresM just implemented a thing that lets you reboot to payload with the regular restart option. And I can confirm it works very well
SciresM just implemented a thing that lets you reboot to payload with the regular restart option. And I can confirm it works very well
according to SciresM you can custom reboot/power off to rcm, payload or normally right? does this means the end of autorcm? if i stick with atmoshpere of course.https://twitter.com/SciresM/status/1092655610489798657
SciresM just implemented a thing that lets you reboot to payload with the regular restart option. And I can confirm it works very well
Yea, you can choose what the restart option does with an option in system_settings.ini. autoRCM is still useful, because sometimes the system can hard freeze and if that happens you can’t reboot to payload/rcm
Not really as the whole point of AutoRCM is to remove the need for a jig which is useful if you're turning off the console. This just lets you switch payloads and CFW without having to manually re-enter RCM.
And contrary to popular belief, AutoRCM is actually useful if your system runs out of battery since that would mean you wouldn't need a jig to reboot back into RCM. It was also immediately debunked the system wouldn't charge with AutoRCM and an empty battery so AutoRCM has plenty of reason to stick around. A jig can always fail but never AutoRCM.
Oh i see, got it wrong. I thought once you setup the power off/reboot button, it would work even if you power off the console. I mean you power off the console and with the power off button you would be able to load hekate or rcm. So it is like the "reboot to payload" thingy but no need to .nro or the uso of homebrew menu right?
This was addressed earlier with a question about why @SciresM doesn't just release the new key (answer: it's illegal). I thought I'd throw in my two cents.
When the 6.2.0 update broke CFW, one of the dilemmas was getting the new master key out to the public. SciresM talked about this dilemma a lot on Discord, coming to the conclusion that there was no legal way to do so. This was resolved by updating Atmosphere to legally generate the key using the Switch itself, but that had the downside of revealing the exploit to Nintendo. This caused them to patch the exploit in 7.0.0.
Now, the same dilemma is likely happening. He has the new key, but there's no way to get the key to the public without revealing the exploit to Nintendo. This is apparently what he's doing with the upcoming Atmosphere update.
I'm concerned that, unless the exploit is unpatchable, this might be a bad idea. One possible solution, since releasing the key is illegal, would be to only release the exploit privately to those who may or may not leak just the key. That way, SciresM doesn't break any laws, and the key becomes public in a way that doesn't reveal the exploit.
Edit: See below about how he's neither releasing the key nor the exploit.
When the 6.2.0 update broke CFW, one of the dilemmas was getting the new master key out to the public. SciresM talked about this dilemma a lot on Discord, coming to the conclusion that there was no legal way to do so. This was resolved by updating Atmosphere to legally generate the key using the Switch itself, but that had the downside of revealing the exploit to Nintendo. This caused them to patch the exploit in 7.0.0.
Now, the same dilemma is likely happening. He has the new key, but there's no way to get the key to the public without revealing the exploit to Nintendo. This is apparently what he's doing with the upcoming Atmosphere update.
I'm concerned that, unless the exploit is unpatchable, this might be a bad idea. One possible solution, since releasing the key is illegal, would be to only release the exploit privately to those who may or may not leak just the key. That way, SciresM doesn't break any laws, and the key becomes public in a way that doesn't reveal the exploit.
Edit: See below about how he's neither releasing the key nor the exploit.
Last edited by Lacius,
He's not releasing the key or the exploit, he outlined his plan on Discord, yesterday I think, for how he's going to work around this problem.
Similar threads
-
- Portal
-
- Portal
-
- Portal
-
- Portal
-
-
-
-
-
@
Sonic Angel Knight:
Or, I also heard that if you use flash memory, it can act as more "RAM" at least windows tell me when I stick a flash drive into it. -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
K3Nv2:
I can think of the design teams process another joystick and no audio or a joystick and mono audio -
-
-
-
-
