Why I chose a hybrid post-quantum design (ML-KEM-768 + X25519) for encrypted cloud storage
I'm building SecVault, a zero-knowledge encrypted cloud storage service. Files are encrypted on your device before upload, so the server never sees plaintext. Here's why I picked a hybrid post-quantum design, and what it does and doesn't give you. The threat: harvest now, decrypt later Cloud files live for years. An attacker who records encrypted data today could decrypt it later if a quantum…
SecVault, a zero-knowledge encrypted cloud storage service, employs a hybrid post-quantum design (ML-KEM-768 + X25519) for safeguarding user data. This choice stems from the recognition that encrypted files exist for extended periods, posing a risk if a quantum computer's capabilities advance further. To counter this threat, SecVault implemented a hybrid key encapsulation mechanism (KEM), combining ML-KEM-768, which is new and currently non-quantum-resistant, with the battle-tested X25519.
Additionally, the service utilizes hybrid signatures (ML-DSA-65 + Ed25519) and AES-256-GCM for file encryption, carried out on the user's device. Argon2id, another cryptographic algorithm, is employed to transform user passwords into encryption keys. Unlike traditional cloud storage services, SecVault enables users to revoke access to their files, and data is stored in Amsterdam, EU.
However, it is crucial to note that this service has not undergone an independent audit nor is it open-source. Currently, SecVault is only accessible via waitlist, offering a Founding Pass that grants users 100 GB of free storage for six months.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
