Documentation
Docs
Technical documentation for the Confium engine, its three deployment modes, and the principles that shape every crate.
-
Architecture
Confium's engine, plugin loader, versioned interfaces, coordinator, and the principles that shape every crate.
-
Three deployment modes
Mode 1 (Peer-to-Peer TC), Mode 2 (PKI Drop-in), Mode 3 (Sovereign PKI). One engine, three integration shapes.
-
Mode 1 — Peer-to-Peer TC
Nodes do threshold cryptography directly. Hours to value. The simplest deployment shape.
-
Mode 2 — PKI Drop-in
Replace single-party keys with threshold keys. Existing PKCS#11 / OpenSSL / JCE consumers keep working unchanged.
-
Mode 3 — Sovereign PKI
Custom certificate formats for institutions where no single party can be trusted. Sovereign over formats, delegation, archival, quorum.
-
Components
The 43-crate Confium Rust workspace, grouped by category. Engine, threshold crypto, PKI, storage, network, Mode 2 adapters, transparency.
-
Security model
Confium's threat model, trust assumptions, and defense-in-depth layers. What the framework protects against and what it expects of operators.
-
Post-quantum migration
Migrate from classical to post-quantum signatures via composite signatures. Software upgrade, not HSM replacement. No certificate re-issuance flag day.
-
Transparency logs
RFC 6962 Merkle transparency logs. Inclusion proofs, consistency proofs, witness gossip, OTS anchoring. How split-view attacks are detected.
-
Getting started
Quickstart hub for Confium — Ruby, Rust, and WASM install commands and pointers into per-binding docs.
-
Comparison
Confium vs HSMs, conventional CAs, KMS, Sigstore, and commercial threshold solutions. Where each fits, where each falls short.
-
Compliance
FIPS 140 mode, jurisdictional algorithm policies, audit log format, and regulatory mapping to eIDAS, HIPAA, FedRAMP, and Common Criteria.
-
Confium CLI
The confium command-line tool — install, manage, and operate Confium plugins, signers, and the local configuration store.
-
FAQ
Common questions about Confium — what it is, how it works, when to use it, and the limits of threshold-native trust infrastructure.
-
confium version
Print the version of the confium CLI and the underlying engine.
-
Troubleshooting
Operational gotchas, common errors, and their fixes for Confium deployments and consumers.
-
confium install
Install a Confium plugin from the registry. Currently a stub awaiting the confium-net HTTP-fetching crate.
-
confium remove
Remove an installed Confium plugin from the local store.
-
confium update
Update an installed plugin to the latest version. Currently a stub awaiting the confium-net HTTP-fetching crate.
-
confium list
List installed Confium plugins, optionally filtered by interface or algorithm.
-
confium info
Show detailed information about an installed Confium plugin.
-
confium search
Search the Confium plugin registry for available plugins.
-
confium trust
Manage the trusted-publisher list — which publishers' plugins the local install will accept.
-
confium config
Read and write local Confium configuration.
-
confiumd
The confiumd daemon — long-running JSON-RPC service for signing sessions, transparency log interaction, and PKI operations.
-
confium-publish
The plugin author's publishing tool — wraps a plugin artifact, signs the manifest, and prepares it for submission to the Confium registry.
-
Tooling
Binaries and adapter libraries shipped by the Confium workspace — beyond the CLI.
-
confium-pkcs11-server
PKCS#11 v3.0 server — exposes Confium threshold signing to existing PKCS#11 consumers (OpenSSL ENGINE, Java SunPKCS11, nginx).
-
confium-openssl-provider
OpenSSL 3.0 provider — exposes Confium threshold signing to modern OpenSSL consumers (nginx, curl, custom C).
-
confium-jce-provider
Java Cryptography Extension provider — exposes Confium threshold signing to Java applications via KeyStore / Cipher / Signature APIs.
-
confium-tls-signer
TLS 1.3 signature callback — high-value domain protection with threshold signing for handshakes.
-
confium-test-harness
NIST MPTS evaluation harness + multi-party threshold simulation runner.
-
Adapters
Deep dives into the Mode 2 adapters — PKCS#11, OpenSSL 3.0, JCE, TLS 1.3. How they wire existing consumers into Confium.
-
PKCS#11 adapter
PKCS#11 v3.0 adapter — expose Confium as a virtual HSM to OpenSSL, Java, nginx, and custom consumers.
-
OpenSSL 3.0 provider adapter
OpenSSL 3.0 provider — expose Confium to modern OpenSSL consumers in-process.
-
JCE provider adapter
Java Cryptography Extension provider — expose Confium to Java applications via KeyStore / Cipher / Signature APIs.
-
TLS 1.3 signer adapter
TLS 1.3 signature callback — threshold signing for high-value domain TLS handshakes.