Hacking Wii U Hacking & Homebrew Discussion

[neobrain]

I released the source of https://code.google.com/p/cdecrypt/

NWPlayer123 I sent you PM

Nice move

You might want to rethink this part though:
printf("It is not allowed to resell, rehost, redistribute\nor include this file in any packages!\n\n");

If you don't intend to allow this, you shouldn't be using the GPL, because that license does allow exactly doing this.

 

[crediar]

Nice move

You might want to rethink this part though:
printf("It is not allowed to resell, rehost, redistribute\nor include this file in any packages!\n\n");

If you don't intend to allow this, you shouldn't be using the GPL, because that license does allow exactly doing this.

Just a relict of the binary version.

 

[Mr. Mysterio]

Would it be possible to imitate the Nintendo servers on a closed network and fake a Wii U system update to trick the Wii U into installing whatever binaries we want? Since the common key is available, it should be possible to decrypt/encrypt the data.

 

[FPSRussi4]

Would it be possible to imitate the Nintendo servers on a closed network and fake a Wii U system update to trick the Wii U into installing whatever binaries we want? Since the common key is available, it should be possible to decrypt/encrypt the data.

I'm not sure, I think the Wii U wouldn't accept the "update data" from any addresses except the NUS ones. I don't know too much though, I hope this is a better explanation/theory then "if it could have been done it would have been".

 

[Damieh79]

Would it be possible to imitate the Nintendo servers on a closed network and fake a Wii U system update to trick the Wii U into installing whatever binaries we want? Since the common key is available, it should be possible to decrypt/encrypt the data.

The first (of many probably) problem with your idea is that you assume a symmetrical type of encryption.
As a simple (but unaccurate) example, say we have an elemental code-signing method. We would be using one key (private, you can call it key A or Alice) to encrypt the software, and another key (public, in every console, key B or Bob) to decrypt it.

So the "common key" you're talking about in this case would be the key B. Since nobody but nintendo has key A, you can't do that.

 

[NWPlayer123]

I'm hesitant to say yes simply because of authentication and signing. I'm not sure how the whole process works though.

 

[Onion_Knight]

Would it be possible to imitate the Nintendo servers on a closed network and fake a Wii U system update to trick the Wii U into installing whatever binaries we want? Since the common key is available, it should be possible to decrypt/encrypt the data.

You can decrypt stuff with the common key, however to encrypt you'd need the private key.

 

[Vegeta]

Is the browser exploit and kernel exploit separate or is the browser exploit required to trigger the kernel exploit?

 

[IbbyPlays]

I'm wondering if it could be that simple. Use the common key to find out how the Wii U gets and installs updates, have a DNS server redirect the wii u to a public server or on of our own, and trick the Wii U into installing a lower firmware as an "update" (no need for the private key since NUsDownloader downloads the encrypted binaries).

 

[SirByte]

You can decrypt stuff with the common key, however to encrypt you'd need the private key.

I guess you mean digitally sign.

But perhaps it's possible one day, like the 3DS today, to downgrade to a lower system firmware version using older official Wii U firmware modules. This might be of interest to get a persistent hack, or an easier exploit (like 'DS Profile' vs. "go to a website and sometimes it doesn't work"), or maybe the Wii U equivalent of an EmuNAND.

Don't think this is weird. If you have a tricky exploit that is based on some critically timed race conditions and only works 1 out of 25 times on average, but once it catches you can then take control and downgrade to a lower firmware and get an exploit that is near 100% reliable, it's worth it.

Hopefully someone has been able to grab the Wii U firmwares from Nintendo before they became deprecated and we'll see "downgrade packs" when/if needed.

 

[WiiuGold]

Hopefully someone has been able to grab the Wii U firmwares from Nintendo before they became deprecated and we'll see "downgrade packs" when/if needed.

Get the firmware off the disc. Same thing

 

[hbk2004v1]

so i just unpacked my brand new wiiu and set it up and it's on firmware 3.1.0 E , am i best to just update it to latest firmware ?

 

[the_randomizer]

Your best bet is to buy Mario Kart 8 and use that to update to 4.1.0.

And you're currently on 5.3.2? Should I do the same?

 

[IbbyPlays]

Make sure you don't have an internet connection when you update by disc!

 

[Damieh79]

so i just unpacked my brand new wiiu and set it up and it's on firmware 3.1.0 E , am i best to just update it to latest firmware ?

I'm so envious. Mine had 5.3.0 so I'm stuck with finding new browser exploits =-(.

 

[hbk2004v1]

I'm so envious. Mine had 5.3.0 so I'm stuck with finding new browser exploits =-(.

wait i thought 5.3.2 was confirmed safe to update to for the exploit ? has this changed now

 

[NWPlayer123]

wait i thought 5.3.2 was confirmed safe to update to for the exploit ? has this changed now

No, he's talking about how we need to find another bug to run code on the latest version, "safe" just means the kernel exploit still works, since it's much more time consuming.

 

[IbbyPlays]

wait i thought 5.3.2 was confirmed safe to update to for the exploit ? has this changed now

The kernel exploit will run on 5.3.2
However, you need a webkit exploit to trigger the kernel exploit. The only publicly released webkit exploit works on 4.0.0-5.1.0

 

[NWPlayer123]

It is possibly safe to update if my bug turns out to be exploitable.

Even if it isn't there are plenty of options.

 

[KungFuzion]

I got home from work today, my kids decided to play mario kart online for the first time in ages & updated from 4.1 to 5.3.2.......after I told them DON'T connect the wii u to the internet.......i'm so gutted. I've been following this thread for months & looking forward to the kernel exploit release. Fingers crossed the new browser exploit can be pulled off or as NWPlayer123 said, "there are plenty of options??" With the news that the kernel exploit is still unaffected on the latest 5.3.2 I guess there is still hope.