Skip to content

Encryption

Henri edited this page Nov 22, 2015 · 5 revisions

Encryption is part of the security features of Peps.

PEPS supports encrypted transport

All connections between client and server are encrypted using TLS.

PEPS supports optional client-side encryption of messages and files.

Encryption is transparent, and applied to all messages and files classified with an "Encrypted" class. We chose not to encrypt everything, as encryption prevents some features (full text search, deduplication, etc.). Encryption uses TweetNaCl to implement curve25519-xsalsa20-poly1305.

Screenshot of the classes definition interface, showing the encryption field. All data tagged by this class will be encrypted.

Encryption relies on PBKDF2 to derive keys from the user password. Note that if a user looses its password, encrypted content will not be recovered.

More information is available in French in the Chiffrement page.