Cryptosystem - Revision history

Zachycatgames: /* Versions */ Add first byte of K4 pubkey

2025-09-28T19:25:05Z

Versions: Add first byte of K4 pubkey

← Older revision		Revision as of 23:25, 28 September 2025
Line 373:		Line 373:
	\|-		\|-
	\| K4		\| K4
	\|		\| 0x6D
	\| Erista prototype retail		\| Erista prototype retail
	\|-		\|-

SciresM: /* Versions */ fix M1-M4

2020-11-07T21:29:04Z

Versions: fix M1-M4

← Older revision		Revision as of 00:29, 8 November 2020
Line 385:		Line 385:
	\|-		\|-
	\| M1		\| M1
	\| ~~0xDD~~		\| 0x19
	\| Mariko prototype development		\| Mariko prototype development
	\|-		\|-
Line 393:		Line 393:
	\|-		\|-
	\| M3		\| M3
			\| 0xDD
			\| Mariko prototype retail (pre-6.0.0)
			\|-
			\| M4
	\| 0x9B		\| 0x9B
	\| Mariko retail		\| Mariko retail

Hexkyz at 19:53, 11 April 2020

2020-04-11T17:53:39Z

Show changes

Ctcaer: Undo revision 6770 by Shchmue (talk) - ("Storage" is used in all other patents and all nv code, docs and binaries

2019-05-02T00:12:03Z

Undo revision 6770 by Shchmue (talk) - ("Storage" is used in all other patents and all nv code, docs and binaries

← Older revision		Revision as of 04:12, 2 May 2019
Line 3:		Line 3:

	* the SBK (Secure Boot Key) in keyslot 14		* the SBK (Secure Boot Key) in keyslot 14
	* the SSK (Secure ~~System~~ Key) in keyslot 15.		* the SSK (Secure Storage Key) in keyslot 15.

	Reads from both of these keyslots are disabled by the bootROM.		Reads from both of these keyslots are disabled by the bootROM.
Line 78:		Line 78:
	\|-		\|-
	\| 15		\| 15
	\| ~~SecureSystemKey~~		\| SecureStorageKey
	\| Bootrom		\| Bootrom
	\| Yes		\| Yes
Line 200:		Line 200:
	\|-		\|-
	\| 15		\| 15
	\| ~~SecureSystemKey~~		\| SecureStorageKey
	\| Bootrom		\| Bootrom
	\| Yes		\| Yes

Shchmue: SSK == "Secure System Key" per https://patents.google.com/patent/US20100070743

2019-04-30T11:41:26Z

SSK == "Secure System Key" per https://patents.google.com/patent/US20100070743

← Older revision		Revision as of 15:41, 30 April 2019
Line 3:		Line 3:

	* the SBK (Secure Boot Key) in keyslot 14		* the SBK (Secure Boot Key) in keyslot 14
	* the SSK (Secure ~~Storage~~ Key) in keyslot 15.		* the SSK (Secure System Key) in keyslot 15.

	Reads from both of these keyslots are disabled by the bootROM.		Reads from both of these keyslots are disabled by the bootROM.
Line 78:		Line 78:
	\|-		\|-
	\| 15		\| 15
	\| ~~SecureStorageKey~~		\| SecureSystemKey
	\| Bootrom		\| Bootrom
	\| Yes		\| Yes
Line 200:		Line 200:
	\|-		\|-
	\| 15		\| 15
	\| ~~SecureStorageKey~~		\| SecureSystemKey
	\| Bootrom		\| Bootrom
	\| Yes		\| Yes

Motezazer: Keyblobs are dead

2018-11-25T13:20:23Z

Keyblobs are dead

← Older revision		Revision as of 16:20, 25 November 2018
Line 352:		Line 352:
	\| 6.0.0-6.1.0		\| 6.0.0-6.1.0
	\| 6		\| 6
	~~\| 1~~
	\|-
	~~\| 6.2.0~~
	~~\| 7~~
	\| 1		\| 1
	\|}		\|}

			Starting from 6.2.0, key generation no longer uses keyblobs.

	== Secure Monitor Init ==		== Secure Monitor Init ==

SciresM: 6.2.0 keygen details

2018-11-24T01:07:24Z

6.2.0 keygen details

@@ Line 171: / Line 171: @@
 |}
@@ Line 217: / Line 251: @@
 .. and on 4.0.0 it was further moved around:
    keyblob_key     /* slot13 */ = aes_unwrap(aes_unwrap(wrapped_keyblob_key, tsec_key /* slot13 */), sbk /* slot14 */)
    cmac_key        /* slot11 */ = aes_unwrap(59c7fb6f.., keyblob_key)
@@ Line 232: / Line 265: @@
    new_per_console_key /* slot13 */ = aes_unwrap(0c9109db.., old_keyblob_key)
    per_console_key     /* slot15 */ = aes_unwrap(4f025f0e.., old_keyblob_key)
 SBK and SSK keyslots are cleared after keys have been generated.
@@ Line 243: / Line 293: @@
 This means that if you have an attack on the bootloader, you need to re-preform it every time they move to a new keyblob.
-Dumping the SBK and TSEC key of any single system should be enough to derive all key material on the system.
+Dumping the SBK and TSEC key of any single system should be enough to derive all key material on the system, prior to 6.2.0.
 The key-derivation is described in more detail [[Package1#Key_generation|here]].

Hexkyz: /* Table of used keyblobs */

2018-11-21T14:06:42Z

Table of used keyblobs

← Older revision		Revision as of 17:06, 21 November 2018
Line 300:		Line 300:
	\| 1		\| 1
	\|-		\|-
	\| 6.0.0		\| 6.0.0-6.1.0
	\| 6		\| 6
			\| 1
			\|-
			\| 6.2.0
			\| 7
	\| 1		\| 1
	\|}		\|}

Shchmue: /* Table of used keyblobs */ 6.0.0

2018-09-19T20:09:52Z

Table of used keyblobs: 6.0.0

← Older revision		Revision as of 00:09, 20 September 2018
Line 296:		Line 296:
	\| 1		\| 1
	\|-		\|-
	\| 5.0.0		\| 5.0.0-5.1.0
	\| 5		\| 5
			\| 1
			\|-
			\| 6.0.0
			\| 6
	\| 1		\| 1
	\|}		\|}

Motezazer: New update + clarifications

2018-03-12T23:39:19Z

New update + clarifications

← Older revision		Revision as of 02:39, 13 March 2018
Line 124:		Line 124:
	\|-		\|-
	\| 13		\| 13
	\| ~~PerConsoleKeyForNewPerConsoleKeyGen~~		\| PerConsoleKeyForFirmwareSpecificPerConsoleKeyGen
	\| [[Package1#Package1ldr\|Package1ldr]]		\| [[Package1#Package1ldr\|Package1ldr]]
	\| Yes		\| Yes
Line 130:		Line 130:
	\|-		\|-
	\| 14		\| 14
	\| ~~StaticKeyForNewPerConsoleKeyGen~~		\| StaticKeyForFirmwareSpecificPerConsoleKeyGen
	\| [[Package1#Package1ldr\|Package1ldr]]		\| [[Package1#Package1ldr\|Package1ldr]]
	\| No		\| No
Line 159:		Line 159:
	\|-		\|-
	\| 13		\| 13
	\| ~~NewPerConsoleKey~~		\| FirmwareSpecificPerConsoleKey
	\| Secure Monitor init		\| Secure Monitor init
	\| Yes		\| Yes
Line 292:		Line 292:
	\| 1		\| 1
	\|-		\|-
	\| 4.0.0		\| 4.0.0-4.1.0
	\| 4		\| 4
			\| 1
			\|-
			\| 5.0.0
			\| 5
	\| 1		\| 1
	\|}		\|}
Line 300:		Line 304:
	On all versions, the key to decrypt [[Package2]] is generated by decrypting a constant seed with the master key. The key is erased after use.		On all versions, the key to decrypt [[Package2]] is generated by decrypting a constant seed with the master key. The key is erased after use.

	Additionally, starting from 4.0.0, the Secure Monitor init will decrypt another constant seed successively with a special per console key and a special static key passed by package1loader, to generate ~~a new~~ per-console key. The operation will erase these special keys passed by package1loader.		Additionally, starting from 4.0.0, the Secure Monitor init will decrypt another constant seed successively with a special per console key and a special static key passed by package1loader, to generate the firmware specific per-console key. The operation will erase these special keys passed by package1loader.

	== Secure Monitor ==		== Secure Monitor ==
	The secure monitor performs some runtime cryptographic operations. See [[SMC]] for what operations it provides.		The secure monitor performs some runtime cryptographic operations. See [[SMC]] for what operations it provides.