Homebrew "Privacy" of ncchinfo.bin, boot9strap and XORPads
- Thread starter Deleted member 340473
- Start date
- Views 2,165
- Replies 4
No, all content files (and therefore their decryption key(s), whether in "official format" to be used with a copy of the official implementation, or as xorpads) are not console-specific (imagine if they were... gamecards would need to be made per-user at inflated prices, separate eShop download urls for every user...)
Note how everyone who uses titlekey-generated tickets ends up with exactly the same ticket, as the only "active" parts for decryption are titleID, titlekey (from the ticket), and encryption mode selection (from the NCCH's header); other parts of the ticket are indeed console-specific (it's actually these parts that make eShop purchases console-specific) but they are not needed for decryption, only for signature verification (which all CFWs skip by default or option)
Note how everyone who uses titlekey-generated tickets ends up with exactly the same ticket, as the only "active" parts for decryption are titleID, titlekey (from the ticket), and encryption mode selection (from the NCCH's header); other parts of the ticket are indeed console-specific (it's actually these parts that make eShop purchases console-specific) but they are not needed for decryption, only for signature verification (which all CFWs skip by default or option)
Last edited by Ryccardo,
The only file that may contain console/user info is a ticket, and only if you extract them exactly as they are stored in the 3DS or try to build a legit CIA using decrypt9/godmode9.
Similar threads
