Some punk who claimed to be a Nintendo engineer lol
where can I find his claims?
Some punk who claimed to be a Nintendo engineer lol
where can I find his claims?
where can I find his claims?
Still, whether or not that guy was from Nintendo or not (if it's the same Dalavin that's everywhere else on the internet, he is), they did publicly disclose an exploit. If Nintendo cares at all about their console's security (and don't assume they don't), they'll see that and patch it.
The patch only consists of moving one line of code down a few lines...
I don't find that to be very reassuring at all, esp. since the future of Wii U hacks is so uncertain. What guarantee, if any, do we have that we'll ever see this Messianic exploit, if ever? Kinda hard not to be negative about it, you know? I don't know how or what to believe anymore.
You can see the exploit right this second by looking through Dalavin's posts, ha.
Go implement it yourself if you don't wanna wait for someone else to, though. Then you'll see why it's taking a while. Lots of little things need to be figured out in advance, tested, and figured out again before a working hack can be made. Assloads of ROP, really.
Damn, because of this douche, Nintendo knows about the exploit (I'm sure he's a squealer for them), yeah, it takes time, I know that, but, see, some of use have updated to 5.2.0 (not 5.3.0), permanently locking us out, right? Right... What does it matter now? Some of us will never be able to use it. As far as I know, only those up to 5.0.0 can actually be benefited when it does release. But those past 5.1.0? They're essentially shit out of luck. So, I don't know why I bother waiting if some can't even use it on the previous FW
As has been said like five billion times before, making a new webkit exploit is a thing that's going to happen as soon as kernel 'sploit work is done. Re: fail0verflow's talks about how easy it is to exploit an outdated browser. Heck, even us and chadderz both have different browser exploits. I doubt chadderz' is patched unless he reported it to nintendo himself.
Yeah, though at this point you should probably just get a second console unless you care disproportionately more about homebrew than actual games.
Yeah, though at this point you should probably just get a second console unless you care disproportionately more about homebrew than actual games.So in other words, being on 5.2.0 won't be an issue unless I update, correct?
Eventually, im currently working with others to develop a userland exploit with sd card access using smash bros .I updated to 5.2.0 through the Smash Bros disc... If I don't update to 5.3.0, is homebrew still possible on the Firmware/Update I have (5.2.0)?
Eventually, im currently working with others to develop a userland exploit with sd card access using smash bros .
The browser exploit isnt being ported to 5.2.0 at this time as MN1 and co are finishing their kernel exploit first.
The browser exploit will be ported eventually though
What would the userland exploit do? Also, would the kernel exploit work on 5.2.0?
Actually, we know better now. Hykem has said it's unpatched, but MN1 has yet to check himself. No word yet on 5.3.1 yet, but 5.3.0 /should/ be fine.So, obviously, being on 5.2.0 is the cutoff (as far as we know) for the exploit. Now, there've been issue with a small % of users who are getting error codes with memory-related issues. Nintendo is aware of it so, what do we do if Nintendo releases a patch and some of us have this issue? I mean, trying to keep this on topic as much as I can, I just hope there some kind of contingency plan.
My thoughts are that if you arent having any issues on 5.2.0, leave it be. If you are having issues on it then, when nintendo releases an patch then just update and wait for the kernel exploit to be ported over. If you're having issues, your console is at risk for a brick.ba bricked console is bad all around
Actually, we know better now. Hykem has said it's unpatched, but MN1 has yet to check himself. No word yet on 5.3.1 yet, but 5.3.0 /should/ be fine.