Nand/private/movable.sed: Difference between revisions
No edit summary |
No edit summary |
||
Line 10: | Line 10: | ||
| 0x4 | | 0x4 | ||
| 0x4 | | 0x4 | ||
| | | u8 [0], [2], and [3] must be zero. When u8 [1] is non-zero, this indicates that the additional 0x20-bytes block at the end of movable.sed exists, thus this enables verifying the AES-MAC. | ||
|- | |- | ||
| 0x8 | | 0x8 | ||
Line 26: | Line 26: | ||
| 0x120 | | 0x120 | ||
| 0x20 | | 0x20 | ||
| | | This data is written to the file when doing a [[System Settings|System Format]]. The original movable.sed from the factory is only 0x120-bytes. The last 0x10-bytes in this block is an AES-MAC over a SHA256 hash, using the same keyslot used for NAND [[Title_Database|dbs]]. This hash is calculated over the first 0x130-bytes of movable.sed. This AES-MAC is verified is during movable.sed verification(before RSA verification). | ||
|} | |} | ||