Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bad BIS keys on my specific unit, already fix in Atmosphere and Lockpick RCM #8

Open
rlaphoenix opened this issue Dec 23, 2022 · 0 comments

Comments

@rlaphoenix
Copy link

rlaphoenix commented Dec 23, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant