ODRE PQC 0.3.1 / RC2

RC2 release verification

Compare the complete ZIP SHA, then verify CMS, the pinned root and signer, signed CRL, publication manifest, inventory, envelope and policy-pin consistency.

The signed publication manifest binds the customer ZIP filename, byte size and SHA-256 to RC2 Release1/g1 and its Final authority.

Product / RC / Release / Closure0.3.1 / RC2 / Release1 / g1
Customer ZIPODRE_PQC_0.3.1_RC2_RELEASE1_CUSTOMER_DELIVERY.zip
Bytes124808730
Customer ZIP SHA-256783C23AD35B4915E78AE9BE256BF15B03F98A064A933433E1F1EDAE1FF7DDF9C
Inner Product ZIP SHA-256DFB74900DDCD12896123362E513C48F9DC4827F87A36DC4F20F41DE99A068798
install-release-pins.json SHA-256BADECDD98CFA4E3F042F429F1F001268FC054BAE62608E8CC05EFDE8307B2873
verifier-policy.json SHA-25615DB35094051465732F9327E5AAFE085ED94D5B6FD19A26F55262941DD3EAFD3
Root SHA-256DBA554D4B1CDB37516AF7EFA25C7F9D0AD5D2BBD6A163CA7D35822D84B9D3EF8
CMS leaf SHA-256E32FD62D8F50E5AB07B3CA1916301DF869269EFAFBA2E961D4F0A5C12795AD5C

CMS / Manifest / Inventory / SHA-256 / Compatibility

Verify the customer archive and the independently approved verifier kit first. Install into a new protected immutable directory, then follow the RC2 Native installation guide.

Preserve existing identity, License, Unit, Lease and device state. Do not reinitialize an existing installation or copy private material to another device.

Validation applies to the exact artifacts and environments in the evidence. It is not third-party certification or a General Availability claim.

RC2 installation and Native commands