D
Deleted User
Guest
Honestly, this is the smartest thing that nintendo has ever done (imo). They used a minor number in the update, and convinced people it was nothing serious.The thing with this one is that, its such a minor number that you don't expect something of this gravity to occur. The scope of the change from 3.0.0 to 3.0.1 is massive because the hole for smhax was probably one of the biggest holes in a system ever. The change over is huge and the R&D team on this did a monstrous amount of work in patching this, but its in a measly 3.0.1 update. Not a 4.0.0 or even 3.1.0. Just 3.0.1, makes you think its some minor update to something tiny somewhere.
There were early warning signs but it took people basically sacrificing a switch to upgrade to then poke at find out just how severe the change was, and it was severe and probably worse than many expected. They burned a lot of fuses from 3.0.0 to 3.0.1 which was the first flag, but then we found out they changed all the keys, they recompiled everything, and slammed the door shut on smhax. And then bulldozed the house for good measure, if you'll allow me to stretch the analogy painfully far. Haha.
The key changes and everything that followed is going to be the biggest issue, though, because anything made post-3.0.1 will carry keys we won't know nor be able to use to decrypt. There's going to be a lot of work done on 3.0.0 or lower from now on because its an easy access point, but this means that any progress on 3.0.1 will be slowed. And 3.0.0 is going to exist as a walled-off ecosystem until someone manages to crack newer firmware to get new keys. No online. No games post 3.0.1. But emulators will be possible now.
But in all honesty, it was probably somebody from Hackerone who reported it.