Technical Guide

How Aegiro stores and protects your data.

This page summarizes Aegiro's cryptographic primitives, threat model, filesystem support matrix, and deep technical references.

Cryptographic Primitives

Key cryptographic components used by Aegiro.

Argon2id

Derives passphrase keys (32-byte output) for vault and recovery flows.

AES-256-GCM

Wraps key material and protects encrypted metadata blocks with integrity.

Kyber512

Provides post-quantum KEM for APFS/USB recovery wrapping and vault DEK access path.

Dilithium2

Signs manifest hashes for authenticity checks in verify/doctor paths.

Threat Model

Threats covered in the current APFS/USB recovery schemes.

ThreatMitigation
Recovery bundle stolen without passphraseStill locked: recovery keys are Argon2id-derived and never stored.
Wrong disk/image paired with a bundleIdentifier assertions plus AAD binding reject cross-target bundle reuse.
Bundle tamperingAES-GCM authentication tags detect modified wrapped secrets.
Nonce reuse concerns in wrapsEach wrap call generates an independent random 12-byte nonce.
Harvest-now/decrypt-later pressureKyber512 KEM protects recovery wrapping in current builds.

Filesystem Support Matrix

Filesystem and workflow support.

Volume typeapfs-volume-encrypt / apfs-volume-decryptusb-container-*usb-vault-pack
APFS (writable)
Non-APFS (exFAT/FAT/NTFS writable)
Read-only / locked media

Legend:supportednot supported

Deep References

Full technical docs and schematics.