Skip to main content

Module pq_provider

Module pq_provider 

Source
Expand description

Post-quantum hybrid TLS crypto-provider policies (#557 / S6 of epic #550).

The owned iroh endpoint uses a provider that offers hybrid X25519MLKEM768 plus classical X25519 because iroh reuses it for public N0 relay and pkarr HTTPS. The owned Hyprstream ALPNs remain hybrid-only at the completed carrier-admission hook, and application-layer HyKEM remains the primary, transport-independent confidentiality guarantee on every path.

Structs§

ProviderPolicyError
The effective process-wide rustls provider does not match hyprstream’s declared external-interoperability policy.

Functions§

install_pq_crypto_provider
Install and validate the external-interoperability provider as rustls’s process-wide default.
internal_mesh_crypto_provider
Provider for an owned internal-mesh connection. Classical fallback is intentionally absent, so an X25519-only peer fails the TLS handshake.
pq_crypto_provider
Provider for an explicitly declared external-interoperability boundary. PQ hybrid is preferred, with classical X25519 retained for non-PQ peers.
validate_internal_mesh_crypto_provider
Validate that a caller-supplied config uses the exact owned-mesh policy. This is intentionally stricter than merely preferring the hybrid group: any classical fallback makes the config unsuitable for an owned boundary.