Difference between revisions of "Process Services PXI"
Jump to navigation
Jump to search
Vgturtle127 (talk | contribs) m (More fixes, yay?) |
|||
| Line 27: | Line 27: | ||
| 0x00060000 | | 0x00060000 | ||
| [[1.0.0-0]] | | [[1.0.0-0]] | ||
| − | | GetRomId. This reads 0x40-bytes from [[Gamecards|gamecard]] command 0xC6(gamecard-uniqueID), and returns the first 0x10-bytes from that since the rest of the command reply is all 0xFF-bytes. | + | | GetRomId. This reads 0x40-bytes from [[Gamecards|gamecard]] command 0xC6 (gamecard-uniqueID), and returns the first 0x10-bytes from that since the rest of the command reply is all 0xFF-bytes. |
|- | |- | ||
| 0x00070000 | | 0x00070000 | ||
Revision as of 04:45, 6 November 2014
| Command Header | Available since system version | Description |
|---|---|---|
| 0x000100C6 | 1.0.0-0 | This crypts a raw message with RSA. |
| 0x00020284 | 1.0.0-0 | SignRsaSha256 |
| 0x00030284 | 1.0.0-0 | VerifyRsaSha256 |
| 0x000401C4 | 1.0.0-0 | EncryptDecryptAes |
| 0x00050284 | 1.0.0-0 | EncryptSignDecryptVerifyAesCcm |
| 0x00060000 | 1.0.0-0 | GetRomId. This reads 0x40-bytes from gamecard command 0xC6 (gamecard-uniqueID), and returns the first 0x10-bytes from that since the rest of the command reply is all 0xFF-bytes. |
| 0x00070000 | 1.0.0-0 | GetRomId2. The first u8 this returns is from GetRomMakerCode, the following 0x10-bytes are from encrypting the 0x10-bytes which GetRomId also returns. This is encrypted with AES-CBC, the regular normal-key and IV set by Process9 for this are loaded from the Process9 .rodata section. |
| 0x00080000 | 1.0.0-0 | GetCTRCardAutoStartupBit |
| 0x00090000 | 1.0.0-0 | GetRomMakerCode |
| 0x000A0000 | 1.0.0-0 | GetLocalFriendCodeSeed |
| 0x000B0000 | 1.0.0-0 | GetDeviceId |
| 0x000C0042 | 1.0.0-0 | GatherEntropy |
| 0x000D0042 | 1.0.0-0 | GenerateRandomBytes |
| 0x000E0042 | 1.0.0-0, removed with 2.0.0-2 | With 2.0.0-2 the system no longer handles this command at all. This was mostly the same as GenerateRandomBytes. |
These RSA commands are an interface for using the RSA engine. The system will hang when it attempts to use a >RSA-2048 RSA bit-size with the RSA engine, since the RSA engine does not support >RSA-2048.