Changes to Auth Manifest Specification

Comparing version 2.1 to 2.0
+2 additions -2 deletions
@@ -1,5 +1,5 @@
11 <div style="font-size: 0.85em; color: #656d76; margin-bottom: 1em; padding: 0.5em; background: #f6f8fa; border-radius: 4px;">
2-📄 Source: <a href="https://github.com/chipsalliance/caliptra-sw/blob/b86bbb793cc236e80b37f3d4359a9758672b70a1/auth-manifest/README.md" target="_blank">chipsalliance/caliptra-sw/auth-manifest/README.md</a> @ <code>b86bbb7</code>
2+📄 Source: <a href="https://github.com/chipsalliance/caliptra-sw/blob/a38c99b60c97df406201e098df1b89e9301a26d1/auth-manifest/README.md" target="_blank">chipsalliance/caliptra-sw/auth-manifest/README.md</a> @ <code>a38c99b</code>
33 </div>
44
55 ## SOC Manifest
@@ -13,7 +13,7 @@
1313 Those signatures are also stored in the Preamble.
1414 The Caliptra firmware's ECC and PQC private keys endorse the manifest's public keys, and these endorsements (signatures) are part of the Preamble as well.
1515
16- *Note: All fields are little endian unless specified*
16+ *Note: Do not treat the entire manifest as little endian. Scalar `u32` fields use little-endian layout. ECC key and signature fields are stored as big-endian `u32` words. Raw byte-array fields, such as image hashes, use the exact byte sequence produced by standard tools like OpenSSL unless a field description explicitly says otherwise.*
1717
1818 | Field | Size (bytes) | Description |
1919 | ---------------------------------- | ------------ | ----------- |