implement doesn't just mean something like a spoon. just because you think they made a mistake does not mean they actually did.Also, implement an exploit? I thinks you mis-typed.
His new exploit doesnt allow kernelmode, all his previous work that is being referred to is using the 4.x KernelMode, using the mset hack for entry, this is entirely different, read what he wrote
What it is, what it isn’t
If you’ve read my (now really old and outdated) article on 3DS hacking, you’ll recall that for a number of reasons, hacking the console happened by chaining multiple exploits with one another. The most widely used hack (used by flashcart teams, myself and a number of other people) reliies on not one but two completely distinct exploits : the mset DS user settings exploit, which gives us arm11 usermode ROP capabilities, through which a FIRM vuln is exploited to obtain arm9 code exec. This last part was fixed with firmware version 5.0, and it’s the real critical part : while there’s a pretty high number of games that could potentially be exploited through saves to do usermode ROP, it’s useless if you don’t have another exploit to chain that gives you code exec capabilities. This is where ssspwn comes in; it essentially replaces the FIRM exploit we had on 4.5 and lets us execute arbitrary code. That’s why the video looks similar to the one I’d done when I got 4.5 code exec : the first stage exploit used is the same, just fine tuned to work on 6.3.
What does that mean ? Simply that because the two exploits are completely separate, there’s no reason to believe that just because the mset bug was fixed in 7.0, so was ssspwn. That’s right; ssspwn has yet to be plugged by Nintendo, and could in theory give us code exex on latest firmware version. This isn’t the case yet because we haven’t really looked for a new entrypoint, but that’s the next step.
Generally speaking, the thing that’s been stopping me (and others) from releasing working exploits has been the fact that they might be used for piracy. Fortunately, that should not be a factor in this case, as by its very nature, ssspwn can not by itself allow piracy. That’s right, it’s the sweet spot that gives us just enough to get awesome homebrew code running in arm11 user mode, but not enough to break the system bad enough to let anyone do whatever the hell they want.
What it is, what it isn’t
If you’ve read my (now really old and outdated) article on 3DS hacking, you’ll recall that for a number of reasons, hacking the console happened by chaining multiple exploits with one another. The most widely used hack (used by flashcart teams, myself and a number of other people) reliies on not one but two completely distinct exploits : the mset DS user settings exploit, which gives us arm11 usermode ROP capabilities, through which a FIRM vuln is exploited to obtain arm9 code exec. This last part was fixed with firmware version 5.0, and it’s the real critical part : while there’s a pretty high number of games that could potentially be exploited through saves to do usermode ROP, it’s useless if you don’t have another exploit to chain that gives you code exec capabilities. This is where ssspwn comes in; it essentially replaces the FIRM exploit we had on 4.5 and lets us execute arbitrary code. That’s why the video looks similar to the one I’d done when I got 4.5 code exec : the first stage exploit used is the same, just fine tuned to work on 6.3.
What does that mean ? Simply that because the two exploits are completely separate, there’s no reason to believe that just because the mset bug was fixed in 7.0, so was ssspwn. That’s right; ssspwn has yet to be plugged by Nintendo, and could in theory give us code exex on latest firmware version. This isn’t the case yet because we haven’t really looked for a new entrypoint, but that’s the next step.
Generally speaking, the thing that’s been stopping me (and others) from releasing working exploits has been the fact that they might be used for piracy. Fortunately, that should not be a factor in this case, as by its very nature, ssspwn can not by itself allow piracy. That’s right, it’s the sweet spot that gives us just enough to get awesome homebrew code running in arm11 user mode, but not enough to break the system bad enough to let anyone do whatever the hell they want.
Well. You know how there were environmentalists and extreme environmentalists(aka tree hugging hippies?)
Hacking consoles have evolved in such a similar way. The basic premise still exists but it has... transcended its original intention of unlock the devices to their full/every potential.
Sounds like this exploit wont be able to install custom apps, use redNAND, or allow for piracy (though I'm just guessing). My 4.5 system wont suddenly lose value
Help me understand please: What can be done WITHOUT kernel access? I understand that somehow means not being able to play backups, but what else does it mean? Basically: What can userland do and not do?
Second question: Is it the nature of the exploit that's blocking kernel access or is it some form of DRM that's being implemented?
Second question: Is it the nature of the exploit that's blocking kernel access or is it some form of DRM that's being implemented?
W/O Kernel Access would mean something like limited modifications to the 3DS. Userland probably just allow you to run Homebrew apps which in my opinion is significantly limited. Region free probably requires kernel access.
Not limited modifications. None. You need to launch exploit every time to run homebrew.
So basically, just what everyone was fearing?
Could you give an example?
From what I understand: A translated game could not exist? Or a romhack? Or even a third-party(as in not smea) backup loader (even if it had some form of verification like Devolution?). Is CFW possible (as in not having to constantly run the exploit through DS profile). Will we be able to have custom "channels" as shown off? Will we be able to inject roms into VC? Running GBA games through the native hardware? NAND emulation for accessing new games and Eshop?
Well.. that sounds awful. What IS going to be allowed? Like.. playing some student's coding homework version of Asteroids? Smea's Portal DS? I guess, maybe, DOOM on the go would be cool..
With the way the scene has been struggling to gather momentum, I doubt anyone will really have interest in it.
ssspwn sounds like a pointless failure. Am I missing something here?
Without kernel mode, you can only "play games". Games will never change the way the system works. I think that's simple enough.
What makes those games different from commercial 3DS roms?
And how do we play games if we can't add a channel to the 3DS homescreen?
Yes. Sounds about right.
You can play homemade tetris, homemade connect four, maybe a gallery app. Stuff like this. The awesome stuff like hacking the firmware, changing background colours, region free, etc etc will be impossible.
I was thinking about updating my 6.2 (or 6.0 or whatever it is I have) sometime soon just because I didn't want to be bothered to update each time I start my console... maybe I should wait for that anyway
Similar threads
-
- Portal
-
- Portal
- No one is chatting at the moment.
