So, what would the hacking groups need to get "keys" for 301+ games? Another major (their words) security flaw on those firmwares?
I remember the old PS3 days where sony changed the keys (if i remember correctely) but people could pirate them anyway until a cartain "big firmware update" when it stopped (maybe sony got to the hackers).
What an amazing thread, helped me to understand the situation a lot.
PS3 had a lv0 hack, which meant everyone had access to the master keys and could decrypt updates then sign and encrypt a CFW based on that update version, as lv0 is boot level, right after the boot loader in fact and before every FW module you could basically do whatever you wanted to everything except the bootloader. You have to remember though that PS3 did not have efuses.
What I don't know is if the efuses are checked even before lv0, maybe at bootloader, god maybe even the bootrom does the check, you'd need the big boys for that level of information.
Regardless though to better understand the hack needed for any type of CFW to bypass the efuses you need, at least, a hack after both Userland and Kernel, essentially:
userland<kernel<lv0<bootloader<bootrom.
^--we are here
we need to be----------^here.
This is why you can't emunand the Switch and then update that, emunand comes after boot and lv0, the fuses don't match.
You need CFW, and for that to run a 3.0.1+ game that needs to be from a decrypted resigned FW and to do that you need the lv0 keys, on a 3.0.1+
You can see how much extra work is needed to even play a 3.0.1+ game, let alone piracy which is another story.
However they wouldn't be called hackers if they followed the rules now would they, and anything could happen.