Changing the cryptography library in your CryptPad server
A tutorial to explain why and how to change the backend cryptography library on your cryptpad server
A tutorial to explain why and how to change the backend cryptography library on your cryptpad server
🇫🇷 Post in French - Nous vous présentons dans quels scénarios CryptPad est sécurisé, et partageons des idées d'actions concrètes pour un usage de CryptPad respectant votre confidentialité.
We show you in which scenario CryptPad is secure, and give you ideas for concrete actions for a safe CryptPad usage.
A guide to setup two-factor authentication (2FA) on your favorite CryptPad instance.
We proudly present the CryptPad white paper summarizing the use of cryptography in CryptPad.
A complete tutorial about Nginx TLS configuration with acme.sh
Something terrible is happening in the EU and we need help to stop it
We have been talking about our project site for a while ... Last week we added an important feature to the site: the list of public CryptPad instances.
Approximately one year ago, we published an article about our intention to follow a biweekly release schedule. Since then, we've thought of every second Tuesday as release day.
CryptPad version 1.14 (Codename Ouroboros) has been released and the most exciting new feature is one you cannot even see.
CryptPad was born on Halloween 2014, at that time it was a skunkworks project inside of XWiki SAS. The UI was hidious green and white and the only feature was the CKEditor based pad. We have come a long way.
We have gotten a lot of questions about the concept of Zero Knowledge, the vision and ethics as well as the exact meaning.
Update: The issue mentioned in this blog post was assigned CVE-2017-1000051 by Distributed Weakness Filing, thanks Martin Gubri for applying for the number.
Links