Expand description
Node identity provider — native key management with HKDF purpose derivation.
Wraps a root Ed25519 signing key and derives purpose-keyed identities via HKDF.
The root key comes from identity_store.rs (file-based) or OS keyring.
HKDF derivation: HKDF-SHA256(ikm=root_seed, info=purpose_bytes) → 32-byte Ed25519 seed.
Same purpose always produces the same keypair from the same root.
Derived pubkeys are tracked automatically — resolve() recognizes both
the root node pubkey and any purpose-derived pubkeys opened via identity_open().
Structs§
- Node
Identity Provider - Native identity provider backed by a root Ed25519 key.
Constants§
- MESH_
KEM_ PURPOSE - HKDF purpose-label namespace for the node’s
#mesh-kemhybrid keyAgreement identity (S1 / #552). Distinct from the Ed25519, JWT, andMESH_MLDSA_PURPOSElabels so the KEM identity is key-separated (PQUIP key separation). Each suite component derives an independent seed under a per-component sub-label"<MESH_KEM_PURPOSE>/<kem>". - MESH_
MLDSA_ PURPOSE - HKDF purpose label for the mesh ML-DSA-65 signing key (#157).
Functions§
- derive_
mesh_ kem_ recipient - Deterministically derive the node’s
#mesh-kemhybrid-KEM recipient keypair (S1 / #552) from its persisted Ed25519 root key — the confidentiality-side parallel ofderive_mesh_mldsa_key. - derive_
mesh_ mldsa_ key - Deterministically derive the node’s mesh ML-DSA-65 signing key from its persisted Ed25519 root/signing key (#157).
- derive_
purpose_ key - Derive a purpose-keyed Ed25519 signing key from a root key.
- mesh_
host_ subject - Build the per-host mesh-peer subject for an enrolled host label (#328).