You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tldr; is that SciresM had to patch the Atmosphere keygen code to work with my specific Hardware.
Lockpick RCM then promptly fixed it as well, but I'm still waiting for biskeydump to apply the fix.
More and more people are at risk of backing up BIS keys with their NAND, to only find out the BIS keys are bad!
This can be incredibly destructive in the situation where a NAND backup is critical.
I can confirm the BIS keys generated by biskeydump v9 are not valid. I've tested their entropy in HacDiskMount and even tried dumping PRODINFO anyway to see if it worked, which it didn't. The keys generated by Atmosphere's auto backup work.
The text was updated successfully, but these errors were encountered:
Please take a look at the first post in this thread for context: https://gbatemp.net/threads/my-switch-is-a-2019-v6-2-0-xaj4008278-unpatched-unit.546996/
The tldr; is that SciresM had to patch the Atmosphere keygen code to work with my specific Hardware.
Lockpick RCM then promptly fixed it as well, but I'm still waiting for biskeydump to apply the fix.
More and more people are at risk of backing up BIS keys with their NAND, to only find out the BIS keys are bad!
This can be incredibly destructive in the situation where a NAND backup is critical.
Atmosphere's fix (released in 0.9.4): Atmosphere-NX/Atmosphere@600d68b
Lockpick_RCM's fix (released in 1.5.0): shchmue/Lockpick_RCM@6540ddc
I can confirm the BIS keys generated by biskeydump v9 are not valid. I've tested their entropy in HacDiskMount and even tried dumping PRODINFO anyway to see if it worked, which it didn't. The keys generated by Atmosphere's auto backup work.
The text was updated successfully, but these errors were encountered: