Dang wish i could read the above posts. I assumed when you listed mario lugie you were referencing. Games
They still have a lot of hookers and blow to go through before they get back to work.really gateway?? you didn't update your blog about the emunand dangers of 9.6? what the actual fuck
get on the goddamn ball. It's been several hours and only takes a few minutes.
this worries me.
Is there any proof as to correlate that the keys are truly random? Because anything that's signed requires the key that originally signed it to work. Which means that whatever these keys sign will have to use the same key again down the road. Which means that they're not truly random.
- And now, N3DS randomly-generated-at-boot keys that prevent emuNAND on N3DS
I think it's just easier not to update until they say they support it. Better to assume it doesn't work.really gateway?? you didn't update your blog about the emunand dangers of 9.6? what the actual fuck
get on the goddamn ball. It's been several hours and only takes a few minutes.
this worries me.
They're a flash cart group, not your overprotective mother.really gateway?? you didn't update your blog about the emunand dangers of 9.6? what the actual fuck
get on the goddamn ball. It's been several hours and only takes a few minutes.
this worries me.
The arm9loader was updated.
Old version of firm generated and initialized keyX for keyslots 0x15, 0x16, 0x18-0x1F. This version keeps the old algorithm for keyslots 0x11, 0x15, 0x18.
For keyslots 0x16, 0x19-0x1F it uses a new key for keyslot 0x11, but the actual algorithm has not been changed. This time the keyslot 0x11 seed is loaded from (nand_sector96+0x10) instead of (nand_sector96+0). They also changed the initialization vector for the 0x19-0x1F key-generation to a new hardcoded key.
Since we don't know the decrypted value at (nand_sector96+0x10), we don't know the new key for keyslot 0x11, and we cannot generate keys for the updated keyslots 0x16, 0x19-0x1F. Thus they plugged their hole and we can no longer decrypt arm9-binary.
On panic, arm9loader now clears keyslots 0x15, 0x16, 0x18, 0x19, 0x19-0x1F. Previous versions only cleared 0-7, 0x15, 0x16.
really gateway?? you didn't update your blog about the emunand dangers of 9.6? what the actual fuck
get on the goddamn ball. It's been several hours and only takes a few minutes.
this worries me.
really gateway?? you didn't update your blog about the emunand dangers of 9.6? what the actual fuck
get on the goddamn ball. It's been several hours and only takes a few minutes.
this worries me.
At worst, people screw themselves in terms of a little lost time. If they update, they'd simply have to format and reinstall emuNAND, start fresh and update using a ROM or .CIA file. Not the end of the world.I dont think they care if a few people get. Screwed theve already made there money
R4i Gold 3DS support too
So 9.6 emunand?The problem isn't so much decrypting the new Process9 executable; it's decrypting all the subsequent NCCH executables that use the new keyslots. There's already a technique to decrypt the 9.6.0 Process9 that several groups found independently. It's not easy to execute, so I don't know whether anyone has done it yet, though...
So 9.6 emunand?
I just got my PH0 x0 screwdriver and got the Dongle yesterday, would you say it's worth hacking the N3ds now or shall I wait till 9.6 emunand comes out?