Expand description
CMS SignedData seal creation for ahu bundles.
Creates a detached CMS SignedData (RFC 5652) over the manifest bytes. The seal proves that a specific producer assembled the bundle; it does not make the OCSP responses more trustworthy (their own signatures do that).
Uses the der 0.8 ecosystem (via cms crate), separate from the OCSP-side der 0.7 types. The p256 signing key bridges between them.
Enums§
- SealKey
- Algorithm-agnostic seal signing key.
Functions§
- create_
cms_ seal - Create a detached CMS SignedData seal over the manifest bytes.
- demo_
ephemeral_ seal_ key - Generate a fresh, random ECDSA P-256 seal key for explicit demo mode (F07).
- ensure_
distinct_ ecdsa_ seal_ key - Prove that the OCSP signer’s key is distinct from the configured seal key (F07).
- generate_
seal_ cert - Generate a self-signed seal certificate for testing/demo use.
- generate_
seal_ cert_ for_ key - Generate a self-signed seal certificate for any
SealKeytype. - load_
or_ generate_ seal_ material - Resolve seal material under the shared F07 policy — the single source of
truth for the seal-material decision, consumed by the configured loader
(
orchestrate::load_seal_materials) and the one-shothoike signpath. (hoike-core’s config validation mirrors the structural rules; it cannot depend onhoike-sign.) - load_
seal_ certificate - Load a configured seal certificate, normalizing PEM or DER input to DER.
- validate_
seal_ materials - Prove the seal key/certificate pair before publication.