Hacking Decrypt WAD contents using openssl command line...

[Red_Squirrel]

Maybe I discover the error, thx to all

 

[Leathl]

I tried to decrypt 4 different contents of the same WAD (so same titlekey and same IV for all).

If it's 4 different files, it's 4 different IV's.
And as tueidj said, use the index, not the content id!

From Wiibrew again:
CODEContent
Start ÂÂÂÂLength ÂÂÂÂDescription
0x00 ÂÂÂÂ4 ÂÂÂÂContent ID
0x04 ÂÂÂÂ2 ÂÂÂÂIndex //These are the first two bytes of the IV, different for each content
0x06 ÂÂÂÂ2 ÂÂÂÂType
0x08 ÂÂÂÂ8 ÂÂÂÂSize
0x10 ÂÂÂÂ20 ÂÂÂÂSHA1 hash

 

[Red_Squirrel]

Yes, my error was the use of the same IV for each content

Thx for the help again

But now another little question: "my" decripted contents (at difference of NUSD dec. contents) have some padding at the end of the file (all 0x00 to fill the hex line).
Is it normal? Could be dangerous for wad installing? And if you know, is there some option in openssl to avoid that padding?

 

[giantpune]

the size must be divisible by 16 or else it will fail to install. padding is there to let it be aligned properly. you can check the TMD for the size it needs to be after padding is added. it is the u64 directly before the hash for each TMD content.

 

[WB3000]

But now another little question: "my" decripted contents (at difference of NUSD dec. contents) have some padding at the end of the file (all 0x00 to fill the hex line).
Is it normal? Could be dangerous for wad installing?

NUSD reads the actual size of the contents from the TMD, and applies that size to the padded contents to accurately size them. Any careful WAD Packer should take notice and pad accordingly. If you were creating a title from scratch, having the decrypted contents padded would alter the size placed in TMD, potentially having issues. Having the padding remain may also interfere with extracting contents that are U8, etc.

 

[Red_Squirrel]

But now another little question: "my" decripted contents (at difference of NUSD dec. contents) have some padding at the end of the file (all 0x00 to fill the hex line).
Is it normal? Could be dangerous for wad installing?

NUSD reads the actual size of the contents from the TMD, and applies that size to the padded contents to accurately size them. Any careful WAD Packer should take notice and pad accordingly. If you were creating a title from scratch, having the decrypted contents padded would alter the size placed in TMD, potentially having issues. Having the padding remain may also interfere with extracting contents that are U8, etc.

So practically I have to delete that extra padding... Thanks for the advice