Hi Frustalupi,

your best bet would be to have Python 2 installed (bakefile needs it) and then just use their latest release. You can find the download here:
https://github.com/vslavik/bakefile/releases

You would need the bakefile-1.2.5.1_beta-bin.tar.bz2. Extract it go into the newly generated directory "bakefile-1.2.5.1_beta" and then use bakefile like this:

Code:

./bkl /path/to/wudecrypt.bkl

I hope that helps

Though I also uploaded the 0.1 binaries here and on Github. I didn't made any changes to the code after that. At least not yet.

 

@link270 Thanks, that was totally my intention. To push cross-platform coding forward, especially in the Wii U scene.

New version out, v0.1.1.
Releases for all three operating systems are attached to the first post and can be found on the Github releases page.

 

@jimmyleen It is a standard C application that only includes standard C headers that come with every linux. It does run on my Arch Linux VM, my Arch Linux server and my Debian server (though I did not test to decrypt an image yet).

Could you take a look at if the application has execution rights?
Furthermore, it is a command-line program. If you tried to execute it from your file explorer, it most probably just closed before you saw it, as the program terminates right after it prints a small usage header to the console if it wasn't called with the needed command-line arguments.

 

@OuahOuah

The "partition identifier" is a two character code for the type of the "partition" on the disc. Every Wii U Disc has different partitions, just like you can have partitions on your HDD. A complete example for a partition name would be "UP000500101004620000000004CF00" for the 5.3.2 update partition on Mario Party 10 (EUR image).

The following partition types are known to me:

• SI: Contains information about the other partitions, for example partition keys for GM partitions (each GM partition has its own key for encryption/decryption)
• UP: Contains a system firmware update
• GI: Never seen it before, though it seems to be something similar to SI
• GM: Contains game data (the "content", "code" and "meta" folder you maybe already know)

SI, UP and GI partitions are encrypted with the disc specific key, while GM partitions are encrypted with a partition-specific key that is stored in TITLE.TIK files in the SI (or GI?) partitions. The TITLE.TIK file itself is encrypted with the Wii U common key (that's why you need the disc specific key and the common key to extract an image).

WUDecrypt allows you to extract only specific types of partitions, as to play a game, you would only need to extract the GM partition and could discard the data from the UP partitions, as you won't want to extract the unneeded system firmware update. Though some curious people may still want to extract everything and that's why WUDecrypt usually does that

 

Most probably, but that's just a guess, they have something special attached to a legit Wii U or something and they can read its memory. The Wii U could store the key somewhere in memory and they know where.

But they could of course also have something very special they built themselves to read the disc itself and to get the title key.

 

@OuahOuah
No, currently, WUDecrypt needs binary files of the keys (like the ones you already get with scene releases). So you cannot just post the key as plaintext into the files. You have to use a hex editor or something similar to get every byte of the key into it's binary form. It should be 16 bytes long afterwards and bytes are two hexadecimal characters long (e.g. D7 FF FF FF FF, and so on).

Though I could also add the possibility to read plaintext keys if the file extension ends with .txt
I will add this as a Feature Request on the Github sources.

 

It's HxD on Windows and Hex Fiend on OSX and wxHexEditor on Linux

 

There's a GitHub Issue about key files
https://github.com/maki-chan/wudecrypt/issues/2

 

Any updates on this, by chance? I'm seeing that the last commit was about a 1m20d ago, so I'm quite curious