- Joined
- Apr 29, 2011
- Messages
- 31,284
- Trophies
- 2
- Age
- 38
- Location
- Dr. Wahwee's castle
- XP
- 18,969
- Country
Mehhhhhh bad memes for days
Still stands, Team f0f isn't reliable IMO.
Mehhhhhh bad memes for days
I know I said now, but I don't mean right nowThey'll release them when they're done
Aight, that's fairI know I said now, but I don't mean right now
I meant that failoverflow should release their hacks since it's patched
Whenever it's done
You know I'm not one who goes around begging for haxAight, that's fair
Okay. I understood what TrustZone, E-fuses, and the other various encryption methods are... but what the hell is KASLR
No, you're goodDoes the Switch have background updating? Mine is at home, not turned on but possibly in sleep mode.
It's not "clean" for the end user yet, as far as I'mm aware. Plus, we don't know that Deja Vu has been totally patched, we just know that the firmware has been hardened against itExactly! They already have it working, and since deja vu is changed again there would be no reason to hold back the exploit? (perhaps somone in the scene can bestow their knowledge upon us)
Thanks, that’s reassuring.No, you're good
That's not all. There's also a reference to a new Switch model that will fix the hardware exploit.
Kernel Address Space Layout Randomization. Basically exactly what it sounds like; the memory sections used by the system kernel are intentionally moved around in a way that is known to the kernel software, but (ideally) unknown to lower-level software, or to an outside attacker. It's designed such that even if an attacker knows about a vulnerability in the kernel, they shouldn't be able to exploit it, because they don't know where the vulnerable spot is anymore.Okay. I understood what TrustZone, E-fuses, and the other various encryption methods are... but what the hell is KASLR
Didn't they try this with the 3DS? It sounds rather familiar...Kernel Address Space Layout Randomization. Basically exactly what it sounds like; the memory sections used by the system kernel are intentionally moved around in a way that is known to the kernel software, but (ideally) unknown to lower-level software, or to an outside attacker. It's designed such that even if an attacker knows about a vulnerability in the kernel, they shouldn't be able to exploit it, because they don't know where the vulnerable spot is anymore.
I believe they did, though by the time they did it on the 3DS, they were basically just plugging leaks on a capsizing ship.Didn't they try this with the 3DS? It sounds rather familiar...