Skip to main content

Encryption

All file data, names, metadata and directory structure are encrypted client side using encryption keys protected by your passphrase. Meaning only someone with the passphrase can restore/view your data.

See here for what additional metadata we store.

Data is protected using an authenticated cipher with 256-bit keys providing both data authenticity (integrity) and confidentiality.

danger

if you loose your passphrase/key it's not possible to recover your data

Supported algorithms

We support either AES-GCM or ChaCha20-Poly1305 which can be selected when you create the repo.

Both algorithms are considered secure but you may have a personal preference for one.

tip

Use AES-GCM if FIPS-140 is required.

Algorithm Performance

Below is a benchmark of the supported algorithms at varying block sizes on an AMD Ryzen 5800x which may influence your decision.

This CPU includes AES-NI which improves the AES speed considerably, without it you can expect to see around a 10x slowdown, making ChaCha20-Poly1305 faster.

tip

AMD Zen and Intel desktop CPU's for the past decade include AES-NI

AlgoBlock sizeSpeed
AES-256/GCM AES-NI16232.607k/s
AES-256/GCM AES-NI64930.43k/s
AES-256/GCM AES-NI5127.20168M/s
AES-256/GCM AES-NI409656.5659M/s
AES-256/GCM AES-NI32768504.514M/s
AES-256/GCM AES-NI2621442.24369G/s
AES-256/GCM AES-NI10485762.70556G/s
ChaCha20Poly130516250k/s
ChaCha20Poly1305641000k/s
ChaCha20Poly13055127.8125M/s
ChaCha20Poly1305409659.5238M/s
ChaCha20Poly130532768357.143M/s
ChaCha20Poly13052621441113.04M/s
ChaCha20Poly130510485761.19712G/s