| customize.dist | ||
| docs | ||
| storage | ||
| www | ||
| .bowerrc | ||
| .dockerignore | ||
| .env | ||
| .flowconfig | ||
| .gitignore | ||
| .jshintignore | ||
| .jshintrc | ||
| .lesshintrc | ||
| .travis.yml | ||
| and_so_it_begins.png | ||
| bower.json | ||
| CHANGELOG.md | ||
| check-account-deletion.js | ||
| check-accounts.js | ||
| config.example.js | ||
| container-start.sh | ||
| cryptofist.png | ||
| delete-inactive.js | ||
| docker-compose.yml | ||
| Dockerfile | ||
| expire-channels.js | ||
| import | ||
| LICENSE | ||
| package.json | ||
| pinned.js | ||
| pinneddata.js | ||
| readme.md | ||
| rpc.js | ||
| runtests.js | ||
| screenshot.png | ||
| server.js | ||
| TestSelenium.js | ||
CryptPad is the Zero Knowledge realtime collaborative editor.
Encryption carried out in your web browser protects the data from the server, the cloud and the NSA. It relies on the ChainPad realtime engine.
Installation
Installing CryptPad is pretty straightforward. You can read all about it in the installation guide.
It also contains information on keeping your instance of CryptPad up to date.
Current version
The most recent version and all past release notes can be found here.
Setup using Docker
See Cryptpad-Docker and the community wiki's Docker page for details on how to get up-and-running with Cryptpad in Docker.
Setup using Ansible
See Ansible Role for Cryptpad.
Security
CryptPad is private, not anonymous. Privacy protects your data, anonymity protects you. As such, it is possible for a collaborator on the pad to include some silly/ugly/nasty things in a CryptPad such as an image which reveals your IP address when your browser automatically loads it or a script which plays Rick Astleys's greatest hits. It is possible for anyone who does not have the key to be able to change anything in the pad or add anything, even the server, however the clients will notice this because the content hashes in ChainPad will fail to validate.
The server does have a certain power, it can send you evil javascript which does the wrong thing (leaks the key or the data back to the server or to someone else). This is however an active attack which makes it detectable. The NSA really hates doing these because they might get caught and laughed at and humiliated in front of the whole world (again). If you're making the NSA mad enough for them to use an active attack against you, Great Success Highfive, now take the battery out of your computer before it spawns Agent Smith.
Still there are other low-lives in the world so using CryptPad over HTTPS is probably a good idea.
Translations
We'd like to make it easy for more people to use encryption in their routine activities. As such, we've tried to make language-specific parts of CryptPad translatable. If you're able to translate CryptPad's interface, and would like to help, please contact us!
You can also see our translation guide.
Contacting Us
You can reach members of the CryptPad development team on Twitter, via our GitHub issue tracker, on our Matrix channel, or by e-mail.
Contributing
We love Open Source and we love contribution. It is our intent to keep this project available under the AGPL license forever but in order to finance more development on this and other FOSS projects, we also wish to sell other licenses to this software. Before making a pull request, please read and sign the Commons Management Agreement.
If you have any questions or comments, or if you're interested in contributing to Cryptpad, come say hi on IRC, #cryptpad on Freenode.
License
This software is and will always be available under the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. If you wish to use this technology in a proprietary product, please contact sales@xwiki.com.