Skip to main content

ensure_bootstrap_pubkeys_hybrid

Function ensure_bootstrap_pubkeys_hybrid 

Source
pub fn ensure_bootstrap_pubkeys_hybrid(
    entries: &HashMap<String, BootstrapPubkey>,
) -> Result<()>
Expand description

Reject a bootstrap-pubkeys map that still carries Ed25519-only service entries.

Every service this node provisions gets a bound ML-DSA-65 key: there is no classical-only install path, so a classical entry here is stale material from a pre-hybrid provisioning run, not a supported configuration. Left alone it does not degrade gracefully — the service is simply never anchored in the post-quantum trust store, and its RPC is later refused with an opaque “no anchored ML-DSA-65 signer key” at verification time. Failing here converts that into an actionable provisioning error.

Deliberately NOT enforced inside load_bootstrap_pubkeys_hybrid: the low-level loader must stay able to read a legacy file so tooling — and this error itself — can report precisely which entries are stale.