Hacking What's most likely going to happen

[IncredibleWhanG]

i doubt they will be any more updates..well maybe one more once they stop selling it etc any hacks released by then will be patched obv they will probabily patch userland also so i guess people might end up sitting on 5.6.0 with a kernel exploit and no user land accsess

 

[darklordrs]

another upper hand is that our IOSU exploit will work on yet another firmware if they patch 1 kernel exploit

Just trying to understand stuff here: because they only patched one of the two kernel exploits, you'd be able to use the other one to into IOSU behind their backs after the update dropped?

 

[MrRean]

IOSU? I thought it was PPC Kernel, or do you have both?

I was just talking in general; sorry
one of them exists that we know of, and if we release 1/2 kernel exploits, that kernel exploit will be patched in an update, but the IOSU bug will still be there

Just trying to understand stuff here: because they only patched one of the two kernel exploits, you'd be able to use the other one to into IOSU behind their backs after the update dropped?

that's the general idea, yeah, since IOSU exploits are more wanted

 

[davetheshrew]

ARM is the key, on boot up 0x01000000 arm loads with no restriction , all protection is off, it can access to ppc mem. Cold, boot.

 

[Dylon99]

I was just talking in general; sorry[emoji14]one of them exists that we know of, and if we release 1/2 kernel exploits, that kernel exploit will be patched in an update, but the IOSU bug will still be there

So after that you could go to IOSU using the Kernel Exploit via userspace, if thats what im understanding.

 

[MrRean]

So after that you could go to IOSU using the Kernel Exploit via userspace, if thats what im understanding.

wouldn't need a kernel exploit to run it

 

[endoverend]

In my opinion, patience is prudence in this situation. It takes the brain of a five year old to understand why the exploit isn't released. If they release it now, it gets patched, which means no more online play, which means worrying about buying consoles on the right firmware, and an long and arduous game of cat and mouse with Nintendo. Or you can wait until we have another exploit and be one step ahead of Nintendo at any given point in time. And unless you're a legitimate capable developer, there's no reason to argue for the first scenario.

 

[Supster131]

I was just talking in general; sorry
one of them exists that we know of, and if we release 1/2 kernel exploits, that kernel exploit will be patched in an update, but the IOSU bug will still be there

Thanks for clarifying! What are the odds of Nintendo actually patching it or taking a while to patch it?
I know a lot of people (myself included) keep on comparing the Wii U with the 3DS. Nintendo has yet to patch the exploit for the 3DS, it still works on the latest firmware, and Nintendo supposedly still cares about the 3DS. If they aren't patching the exploit for the 3DS, what are the odds they patch the exploit for the Wii U?

 

[MRJPGames]

wouldn't need a kernel exploit to run it

So there are already 2 exploits that give kernel access? Because IOSU = kernel aswell. So why is there no release with 2 exploits that will get the elite haxors there precious kernel, or did Hykem not share with mn1 and others?

 

[MrRean]

Thanks for clarifying! What are the odds of Nintendo actually patching it or taking a while to patch it?
I know a lot of people (myself included) keep on comparing the Wii U with the 3DS. Nintendo has yet to patch the exploit for the 3DS, it still works on the latest firmware, and Nintendo supposedly still cares about the 3DS. If they aren't patching the exploit for the 3DS, what are the odds they patch the exploit for the Wii U?

I can't quite answer that, but it costs quite a bit to release an update (and have it approved)...but I still don't know what their mindset is.

So there are already 2 exploits that give kernel access? Because IOSU = kernel aswell. So why is there no release with 2 exploits that will get the elite haxors there precious kernel, or did Hykem not share with mn1 and others?

MN1 has enough information to duplicate it, yeah

 

[Dylon99]

wouldn't need a kernel exploit to run it

Straight from userspace? Damn that'd be nice. And IOSU is permanent so no need to go to the browser every single time. Thanks for clarifying[emoji14]

 

[MRJPGames]

In my opinion, patience is prudence in this situation. It takes the brain of a five year old to understand why the exploit isn't released. If they release it now, it gets patched, which means no more eonline play, which means worrying about buying consoles on the right firmware, and an long and arduous game of cat and mouse with Nintendo. Or you can wait until we have another exploit and be one step ahead of Nintendo at any given point in time. And unless you're a legitimate capable developer, there's no reason to argue for the first scenario.

You mean what we already have right now...

 

[endoverend]

You mean what we already have right now...

Well technically, yeah, but the choice to release the exploit was made after it was patched. There was no point in withholding a patched exploit. This situation is different.

 

[Donzi]

So how far away is the second exploit from being completed? Surely the first could be released a few weeks before the second is finished and it would still have the same outcome?

 

[the_randomizer]

Well technically, yeah, but the choice to release the exploit was made after it was patched. There was no point in withholding a patched exploit. This situation is different.

At the very least, we now know where it stands and that it's a matter of waiting till an alt kernel exploit is created, a contingency plan if you will.

 

[IncredibleWhanG]

ARM is the key, on boot up 0x01000000 arm loads with no restriction , all protection is off, it can access to ppc and mem. Cold, boot.

is this not what is needed?

 

[Farowe]

Or you can wait until we have another exploit and be one step ahead of Nintendo at any given point in time.

Or you can wait for the console to stop being supported and have an exploit that will remain unpatched til the end of time, with a dead community of course.

 

[MRJPGames]

Well technically, yeah, but the choice to release the exploit was made after it was patched. There was no point in withholding a patched exploit. This situation is different.

I know, but that was you should have given that argument the first time instead of saying that the shit we are in right now will return (which it will but only after ninty fixes it so we do get a short period (at least) of blissful hacking happiness).

 

[davetheshrew]

is this not what is needed?

from reading through a ton of stuff today, id say thats a great avenue to explore, but I am not a dev.

 

[MRJPGames]

So how far away is the second exploit from being completed? Surely the first could be released a few weeks before the second is finished and it would still have the same outcome?

It often hard to predict if an exploit is going to work, but I do agree that if they know they have an entrypoint that they know they can exploit they should already release

--------------------- MERGED ---------------------------

ARM is the key, on boot up 0x01000000 arm loads with no restriction , all protection is off, it can access to ppc mem. Cold, boot.

So where's the release XD