AES Registers - Revision history

TimmSkiller at 12:37, 22 December 2024

2024-12-22T11:37:59Z

← Older revision		Revision as of 14:37, 22 December 2024
Line 482:		Line 482:
	\| -		\| -
	\| No		\| No
			\|-
			\| 0x20
			\| [[System_SaveData\|System Save Data]] encryption key during [[System_Transfer\|System Transfers]]. See [[System_Transfer#System_Save_Data_Transfer\|System Save Data Transfer]].
			\| Bootrom.
			\| NATIVE_FIRM
			\| NATIVE_FIRM
			\| Yes
	\|-		\|-
	\| 0x24		\| 0x24

TimmSkiller at 13:36, 18 December 2024

2024-12-18T12:36:10Z

← Older revision		Revision as of 15:36, 18 December 2024
Line 582:		Line 582:
	\|-		\|-
	\| 0x36		\| 0x36
	\| ~~Unknown.~~ Used by friends module.		\| Used by the [[Friend_Services\|the friends module]] for [[Friend_Services#Approach_Contexts\|ApproachContext]] encryption. See [[FRDU:GetMyApproachContext]].

	See [[~~PSPXI~~:~~EncryptDecryptAes\|EncryptDecryptAes~~]].
	\| Bootrom.		\| Bootrom.
	\| Bootrom.		\| Bootrom.

EvilFlight at 10:30, 28 July 2020

2020-07-28T08:30:00Z

← Older revision		Revision as of 12:30, 28 July 2020
Line 575:		Line 575:
	\| Movable.sed key.		\| Movable.sed key.

	This is the keyslot used for movable.sed encryption + AES-CBC MAC with the import/export [[FSPXI:ImportIntegrityVerificationSeed\|commands]].		This is the keyslot used for movable.sed encryption + AES-CBC MAC with the import/export [[FSPXI:ImportIntegrityVerificationSeed\|commands]]. The keyYs used for crypto/CMAC are different, but both can be found in process9 rodata.
	~~\| Bootrom~~.
	\| Bootrom.		\| Bootrom.
			\| NATIVE_FIRM.
	\| -		\| -
	\| Yes		\| Yes

Guiand: Fix typo

2019-12-15T08:15:46Z

Fix typo

← Older revision		Revision as of 11:15, 15 December 2019
Line 243:		Line 243:
	=== AES_CNT.input_word_order ===		=== AES_CNT.input_word_order ===

	If reversed, writes to AES_KEY*FIFO and AES_WRFIFO fill the FIFO backwards. For AES_WRFIFO, this means that every 16-byte block will have its words in the reverse order, but the order of these blocks remains the same. ~~AES_CNT~~ is unaffected by this field. AES_MAC?		If reversed, writes to AES_KEY*FIFO and AES_WRFIFO fill the FIFO backwards. For AES_WRFIFO, this means that every 16-byte block will have its words in the reverse order, but the order of these blocks remains the same. AES_CTR is unaffected by this field. AES_MAC?

	=== AES_CNT.output_word_order ===		=== AES_CNT.output_word_order ===

Guiand: Clarify endianness and word order docs

2019-12-15T03:26:40Z

Clarify endianness and word order docs

@@ Line 232: / Line 232: @@
 == Endianness and word order ==
-When writing to the AES_CTR, AES_MAC or AES_KEY0/1/2/3 register, the hardware will process the written data according to the current input endianness specified in AES_CNT. This means that the byte ordering within each word is endian swapped accordingly but the word ordering of the register remains little endian.
 == CCM mode pitfall ==

WinterMute: /* Endianness and word order */

2017-10-23T06:28:00Z

Endianness and word order

← Older revision		Revision as of 10:28, 23 October 2017
Line 232:		Line 232:

	== Endianness and word order ==		== Endianness and word order ==
	When writing to the AES_CTR, AES_MAC or AES_KEY0/1/2/3 register, the hardware will process the written data according to the current input endianness specified in AES_CNT. ~~However,~~ the ~~current specified input~~ word ~~order will not be honored for this register, and always defaults to reversed word order. Therefore, for normal~~ word ~~order,~~ the ~~reversal must be carried out manually if required~~.		When writing to the AES_CTR, AES_MAC or AES_KEY0/1/2/3 register, the hardware will process the written data according to the current input endianness specified in AES_CNT. This means that the byte ordering within each word is endian swapped accordingly but the word ordering of the register remains little endian.

	== CCM mode pitfall ==		== CCM mode pitfall ==

TuxSH: lol it was already documented on gbatek

2017-02-09T19:57:51Z

lol it was already documented on gbatek

← Older revision		Revision as of 22:57, 9 February 2017
Line 14:		Line 14:
	\|-		\|-
	\| style="background: green" \| Yes		\| style="background: green" \| Yes
	\| [[#~~AES_MACBLKCNT~~\|AES_MACBLKCNT]]		\| [[#AES_MACEXTRABLKCNT\|AES_MACBLKCNT]]
	\| 0x10009004		\| 0x10009004
	\| 2		\| 2
Line 172:		Line 172:
	Changing the input word order triggers the key/keyX/keyY FIFOs to be flushed.		Changing the input word order triggers the key/keyX/keyY FIFOs to be flushed.

	== ~~AES_MACBLKCNT~~ ==		== AES_MACEXTRABLKCNT ==
	(CCM-MAC length)>>4, i.e. the ~~size~~ of ~~the~~ CCM-MAC ~~to work with, in blocks~~		(CCM-MAC extra data length)>>4, i.e. the number of block of CCM-MAC extra data.

	== AES_BLKCNT ==		== AES_BLKCNT ==

TuxSH: AES_MACBLKCNT

2017-02-09T16:59:42Z

AES_MACBLKCNT

← Older revision		Revision as of 19:59, 9 February 2017
Line 12:		Line 12:
	\| 4		\| 4
	\| RW		\| RW
			\|-
			\| style="background: green" \| Yes
			\| [[#AES_MACBLKCNT\|AES_MACBLKCNT]]
			\| 0x10009004
			\| 2
			\| W
	\|-		\|-
	\| style="background: green" \| Yes		\| style="background: green" \| Yes
	\| [[#AES_BLKCNT\|AES_BLKCNT]]		\| [[#AES_BLKCNT\|AES_BLKCNT]]
	\| ~~0x10009004~~		\| 0x10009006
	\| 4		\| 2
	\| W		\| W
	\|-		\|-
Line 165:		Line 171:

	Changing the input word order triggers the key/keyX/keyY FIFOs to be flushed.		Changing the input word order triggers the key/keyX/keyY FIFOs to be flushed.

			== AES_MACBLKCNT ==
			(CCM-MAC length)>>4, i.e. the size of the CCM-MAC to work with, in blocks

	== AES_BLKCNT ==		== AES_BLKCNT ==
			(Data length)>>4, i.e. the number of blocks to process
	~~{\| class="wikitable" border="1"~~
	~~! Bit~~
	~~! Description~~
	\|-
	~~\| 31-16~~
	\| (Data length)>>4 (i.e. the number of blocks to process)
	\|}

	== AES_WRFIFO/AES_RDFIFO ==		== AES_WRFIFO/AES_RDFIFO ==

Yellows8: /* Keyslot ranges */

2017-01-11T21:58:02Z

Keyslot ranges

← Older revision		Revision as of 00:58, 12 January 2017
Line 266:		Line 266:
	\| SSL cert key.		\| SSL cert key.
	\| Same for all.		\| Same for all.
	\| Same for all.		\| Same for all, normalkeys-only.
	\| style="background: ~~red~~" \| No		\| style="background: orange" \| The keyXs are console-unique, however the normalkeys setup by Boot9 later during keyinit are not console-unique.
	\|-		\|-
	\| 0x10-0x17		\| 0x10-0x17
	\| -		\| -
	\| ~~Not set~~.		\| Set for all except 0x11..0x13. Keydata is different for these.
	\| ~~Not set~~.		\| Normalkey, same for all except the last 4 are all different.
	\| -		\| -
	\|-		\|-
Line 278:		Line 278:
	\| Never used.		\| Never used.
	\| Same for all.		\| Same for all.
	\| Same for all.		\| Same for all, normalkeys-only.
	\| style="background: ~~green~~" \| ~~Yes~~		\| style="background: orange" \| The keyXs are console-unique, however the normalkeys setup by Boot9 later during keyinit are not console-unique.
	\|-		\|-
	\| 0x1C-0x1F		\| 0x1C-0x1F
	\| Never used.		\| Never used.
	\| Same for all.		\| Same for all.
	\| Same for all.		\| Same for all, normalkeys-only.
	\| style="background: ~~green~~" \| ~~Yes~~		\| style="background: orange" \| The keyXs are console-unique, however the normalkeys setup by Boot9 later during keyinit are not console-unique.
	\|-		\|-
	\| 0x20-0x23		\| 0x20-0x23
	\| Never used.		\| Never used.
	\| Same for all.		\| Same for all.
	\| Same for all.		\| Same for all, normalkeys-only.
	\| style="background: orange" \| ~~Normalkey is~~ not~~. keyX is. keyY unknown~~.		\| style="background: orange" \| The keyXs are console-unique, however the normalkeys setup by Boot9 later during keyinit are not console-unique.
	\|-		\|-
	\| 0x24		\| 0x24
	\| Never used.		\| Never used.
	\| Individually set.		\| Individually set.
	\| Individually set.		\| Individually set, normalkey-only.
	\| style="background: orange" \| ~~Normalkey~~ is not~~. keyX is. keyY unknown~~.		\| style="background: orange" \| The keyX is console-unique, however the normalkey setup by Boot9 later during keyinit is not console-unique.
	\|-		\|-
	\| 0x25-0x27		\| 0x25-0x27
	\| -		\| -
	\| Not set.		\| Not set.
	\| ~~Not set~~.		\| Same for all, normalkeys-only. Same keydata as keyslot 0x24.
	\| -		\| style="background: red" \| No
	\|-		\|-
	\| 0x28-0x2B		\| 0x28-0x2B
	\| Never used.		\| Never used.
	\| Individually set.		\| Individually set.
	\| Individually set.		\| Individually set, normalkeys-only. Keyslot 0x28 has same normalkey as keyslot 0x24.
	\| style="background: orange" \| ~~Normalkey~~ is not~~. keyX is. keyY unknown~~.		\| style="background: orange" \| The keyX is console-unique, however the normalkey setup by Boot9 later during keyinit is not console-unique.
	\|-		\|-
	\| 0x2C-0x2F		\| 0x2C-0x2F
	\| Various uniques.		\| Various uniques.
	\| Same for all.		\| Same for all.
	\| Same for all, ~~probably~~.		\| Same for all, normalkeys-only.
	\| style="background: red" \| No		\| style="background: red" \| No
	\|-		\|-
Line 320:		Line 320:
	\| Various uniques.		\| Various uniques.
	\| Same for all.		\| Same for all.
	\| Same for all, ~~probably~~.		\| Same for all, normalkeys-only.
	\| style="background: red" \| No		\| style="background: red" \| No
	\|-		\|-
Line 326:		Line 326:
	\| Various uniques.		\| Various uniques.
	\| Same for all.		\| Same for all.
	\| Same for all, ~~probably~~.		\| Same for all, normalkeys-only.
	\| style="background: red" \| No		\| style="background: red" \| No
	\|-		\|-
Line 332:		Line 332:
	\| Various uniques.		\| Various uniques.
	\| Same for all.		\| Same for all.
	\| ~~Different~~ for all.		\| Same for all, normalkeys-only.
	\| style="background: red" \| No		\| style="background: red" \| No
	\|-		\|-
Line 338:		Line 338:
	\| Various uniques.		\| Various uniques.
	\| Individually set.		\| Individually set.
	\| Individually set.		\| Individually set, normalkeys-only. Keyslot 0x3C has same normalkey as 0x38-0x3B.
	\| style="background: red" \| No		\| style="background: red" \| No
	\|}		\|}

Yellows8: /* AES key-init */

2017-01-11T21:21:05Z

AES key-init

← Older revision		Revision as of 00:21, 12 January 2017
Line 686:		Line 686:
	* The last initialized keyslot is 0x3F, via normalkey. The keydata for this is copied to 0xFFF00618. This is for restoring the keydata when non-NAND FIRM boot ''fails'', since those use keyslot 0x3F with other keydata.		* The last initialized keyslot is 0x3F, via normalkey. The keydata for this is copied to 0xFFF00618. This is for restoring the keydata when non-NAND FIRM boot ''fails'', since those use keyslot 0x3F with other keydata.
	* Lastly it clears the 0x40-bytes at tmpbuf with the u32 loaded from bootrom_dataptr(the word following the above keyslot 0x3F keydata), then returns.		* Lastly it clears the 0x40-bytes at tmpbuf with the u32 loaded from bootrom_dataptr(the word following the above keyslot 0x3F keydata), then returns.

			The keyslots are initialized with the same order of keyslots+keydata_type listed below:

			Console-unique keydata, after the initialization for the key-generation keyslot(0x3F):
			0x04..0x07 keyX
			0x08..0x0B keyX
			0x0C..0x0F keyX
			0x10 keyX
			0x14..0x17 keyX
			0x18..0x1B keyX
			0x1C..0x1F keyX
			0x20..0x23 keyX
			0x24 keyX
			0x28..0x2B keyX

			Common keydata:

			0x2C..0x2F keyX
			0x30..0x33 keyX
			0x34..0x37 keyX
			0x38..0x3B keyX
			0x3C..0x3F keyX
			0x04..0x0B keyY
			0x0C..0x0F normalkey
			0x10..0x13 normalkey
			0x14..0x17 normalkey
			0x18..0x1B normalkey
			0x1C..0x1F normalkey
			0x20..0x23 normalkey
			0x24..0x27 normalkey
			0x28..0x2B normalkey
			0x2C..0x2F normalkey
			0x30..0x33 normalkey
			0x34..0x37 normalkey
			0x38..0x3B normalkey
			0x3C..0x3F normalkey