Eh, it at least took me some google predictions to find out where it was. Not really hard though, no.I thought that it was obvious enough.
I'm slightly retarded okay? Sheesh..I thought that it was obvious enough.
Ok, this may sound naïve as hell, but isn't it true that you can't copyright a calculation? Aren't the posted things in fact, calculated hashes, and not the actual keys?i'd rather not leak keys and so ive been working to generate most of them.. but it comes down to the fact that you'll need nand key2. So I have yet to figure out what im doing about that lol. Also instead of rushing a release ill work on doing that tomorrow since i have to get up for work in 4 hrs. :x
I lost track of time.
Hmmm the SHA-256 of the key I found there is different =/
Try taking the entire key, pasting it into a hex editor, then checking the SHA-256 of the file itself. If you're pasting the ascii values of the key through SHA-256 it won't come up correctly. I was having the same issue.
Try taking the entire key, pasting it into a hex editor, then checking the SHA-256 of the file itself. If you're pasting the ascii values of the key through SHA-256 it won't come up correctly. I was having the same issue.
So that long ass hex string is just one big ass key? or multiple keys just one after the other? just curious.
Just know that we are in a good way right now.I am SO lost....
Just know that we are in a good way right now.
I wonder if this key or group of keys that was leaked is related to this:
"I dumped OTP registers on N3DS, which gave me access to 0x200 bytes of NAND keys " <- 0x200 == 512 bytes, so is this pastebin containing the NAND key(s)? Or is that console unique, and the pastebin is something else that we still needed?
Sounds like it.. I'm just over the walls with the progress being made.From what I am seeing, to make use of the 9.6+ emunand users will likely be required to find their own key? Sounds like Reisyukaku intends to try and make this painless as possible?