Hacking Wii U Hacking & Homebrew Discussion

[VinsCool]

This entire thread is confusing me. People are saying they are glad they didn't update their 4.x Wii U but the exploit should work on 5.x? NWPlayer123 said it was safe to update fully (i'm on 5.2.0 from smash)?

Browser exploit usermode is patched on 5.1.1 and up. That's why. Kernel exploit is still possible on 5.3.2, but we also need an entry point.

 

[FPSRussi4]

Browser exploit usermode is patched on 5.1.1 and up. That's why. Kernel exploit is still possible on 5.3.2, but we also need an entry point.

They're working on porting it as well.

 

[Adeka]

Browser exploit usermode is patched on 5.1.1 and up. That's why. Kernel exploit is still possible on 5.3.2, but we also need an entry point.

Ah good to know. Lets find that entry point

I'm curious if the web browser exploit needs to be launched every time like the go.gateway-3ds exploit or does it install straight onto the Wii U like the homebrew channel

 

[NWPlayer123]

Ah good to know. Lets find that entry point

I'm curious if the web browser exploit needs to be launched every time like the go.gateway-3ds exploit or does it install straight onto the Wii U like the homebrew channel

The former, as mentioned numerous times (should probably add it to my FAQ), you'd have to defeat the loader to install anything. Until you do that it has to be run every time.

 

[Adeka]

The former, as mentioned numerous times (should probably add it to my FAQ), you'd have to defeat the loader to install anything. Until you do that it has to be run every time.

Ah That kind of sucks. Update nag is going to be very annoying. Hopefully a simple homebrew can do something about the update nag

 

[IbbyPlays]

Ah That kind of sucks. Update nag is going to be very annoying. Hopefully a simple homebrew can do something about the update nag

Someone made a public DNS server that can block the nag and updates altogether. If you search through the threads you will probably find it quickly.

 

[IbbyPlays]

So have the devs worked out the issue with threading?

 

[TotalInsanity4]

Someone made a public DNS server that can block the nag and updates altogether. If you search through the threads you will probably find it quickly.

This was taken down by the company hosting the server after the IP was used by a malicious hacker to attack some website (since the IP was public)

Needless to say, black hat hackers suck

 

[dojafoja]

Someone made a public DNS server that can block the nag and updates altogether. If you search through the threads you will probably find it quickly.

If you are talking about ninja_karvers public dns server, he shut it down. Because it was public it was picked up and being used by someone in a DoS attack.

Edit: Ninj'd by TotalInsanity4 lol

 

[Marionumber1]

So have the devs worked out the issue with threading?

We discovered that we'll need to build a new ROP chain, since we can't use an existing library function for what we were doing.

 

[IbbyPlays]

We discovered that we'll need to build a new ROP chain, since we can't use an existing library function for what we were doing.

That has to delay the kernel exploit a lot. Doesn't it. Still being an optimist.

 

[Marionumber1]

That has to delay the kernel exploit a lot. Doesn't it. Still being an optimist.

Not a lot, but somewhat. However, we're pretty confident that doing so will resolve the timing issues.

 

[NWPlayer123]

Success

inb4 people start asking for release date

 

[RCJayce]

Success

inb4 people start asking for release date

The dream is alive! Thanks guys! Now we have to wait a little more.

 

[st4rk]

Success

inb4 people start asking for release date

ToCToU ?

 

[Marionumber1]

ToCToU ?

Quite a bit more complex.

 

[st4rk]

Quite a bit more complex.

Ah nice =)

 

[Mr. Mysterio]

Success

inb4 people start asking for release date

YAY!!

Does this mean you and Marionumber1 have rebuilt the ROP chain already? Or is that for another part of the exploit.

 

[NWPlayer123]

Does this mean you and Marionumber1 have rebuilt the ROP chain already? Or is that for another part of the exploit.

Now that the race attack succeeded, we just need to modify the syscall table to give us arbitrary kernel read/write, and then build from there.This race was the hard part, the rest is trivial

 

[Mr. Mysterio]

Now that the race attack succeeded, we just need to modify the syscall table to give us arbitrary kernel read/write, and then build from there.This race was the hard part, the rest is trivial

Can I ask for an (approximate) release date yet?