← Back to CoreSeal Home

Zero-Knowledge Security Architecture

All files and metadata are encrypted on-device before hitting flash memory. Keys are derived using PBKDF2/Argon2id and never uploaded to any server. Complete offline autonomy with no backdoors.

Cryptographic Pipeline

[User Master Credentials] ──> [PBKDF2 / Argon2id KDF + Cryptographic Salt] │ ▼ [256-bit Master Key Material] │ ┌────────────────────┴────────────────────┐ ▼ ▼ [AES-256-GCM Vault Data] [Encrypted File Metadata] (96-bit Random Nonce / Tag) (On-Device SQLite Encrypted) │ │ ▼ ▼ [Local Flash Storage (.cseal)] [Zero Remote Network Leak]

1. Authenticated Encryption (AES-256-GCM)

Every file is partitioned and encrypted using AES-256 in Galois/Counter Mode. GCM provides both confidentiality and built-in cryptographic authentication, verifying that no ciphertext modification or bit-flipping attack has occurred prior to decryption.

2. Key Derivation Function (KDF)

Key derivation employs memory-hard password stretching via Argon2id (or configured high-iteration PBKDF2-HMAC-SHA256) combined with a cryptographically secure random device salt, mitigating rainbow-table and GPU-accelerated dictionary attacks.

3. Zeroize Memory Protection

Critical cryptographic primitives implement the Rust Zeroize trait. When the user exits the application, locks the screen, or activates the panic lock gesture, sensitive key buffers in memory are actively overwritten with zeroes to minimize cold-boot exposure.