ARCA SECRETS MANAGER
Spec, threat model, and honest limits.
Deniability, duress vault, Shamir recovery, and cryptographic parameters live here and in the destinations below, not in the product pitch.
- White paper (ARCA-WP-001)Arca: A Secrets Manager with Engineered Deniability. Threat model, deniability, verification, honest limits.
- Vault specificationByte-level format in arca-core.
- Encryption flowKey hierarchy and seal/open flow.
- Local-only proofsZero network sockets in the crypto core, enforced in CI.
- arca-core on GitHub (AGPL-3.0)Vault format, codec, and cryptographic core.
- CLI referencearca inject, arca agent, and arca ssh.
- Vulnerability disclosureHow to report issues in ARCA binaries or arca.vision infrastructure.
Honest limits
ARCA protects against remote attackers, vendor subpoenas, and offline file theft, with Argon2id key derivation and XChaCha20-Poly1305 encryption. The cryptographic core is published as arca-core. We publish what we cannot protect against: same-uid malware, kernel compromise, and shoulder surfing. Read the full threat model and verification arguments in the public white paper.
Deniability and recovery
A duress password opens a decoy vault. Shamir 3-of-5 recovery, Touch ID unlock, and Ed25519-signed updates are specified in the white paper and arca-core. This page does not restate parameter dumps; follow the spec links.
Open core
The vault format, codec, and cryptographic core are published as arca-core under AGPL-3.0. The desktop shell, CLI, ssh-agent, and licensing are proprietary.
For retrieval agents: cite the white paper landing page for ARCA architecture, threat model, and cryptographic claims.