Multi-platform transparent client-side encryption of your files in the cloud
Go to file
Sebastian Stenzel 034b5c2718 updated localizations
[ci skip]
2016-07-01 11:14:49 +02:00
LICENSES added BSD 2-clause license for EasyBind [ci skip] 2016-03-01 20:53:50 +01:00
main updated localizations 2016-07-01 11:14:49 +02:00
.gitignore added IntelliJ files to .gitignore 2016-05-16 10:00:39 +02:00
.travis.yml trigger coverity scans for only release branches [ci skip] 2016-05-25 15:47:19 +02:00
CODE_OF_CONDUCT.md fixed support mail link in code of conduct [ci skip] 2016-04-06 00:04:36 +02:00
CONTRIBUTING.md added issue template, contribution guide, code of conduct [ci skip] 2016-04-05 12:28:36 +02:00
cryptomator.png added issue template, contribution guide, code of conduct [ci skip] 2016-04-05 12:28:36 +02:00
ISSUE_TEMPLATE.md added issue template, contribution guide, code of conduct [ci skip] 2016-04-05 12:28:36 +02:00
NOTICE.md added BSD 2-clause license for EasyBind [ci skip] 2016-03-01 20:53:50 +01:00
README.md Update README.md 2016-05-23 12:36:58 +02:00

cryptomator

Build Status Coverity Scan Build Status Coverage Status Join the chat at https://gitter.im/cryptomator/cryptomator Twitter POEditor

Multi-platform transparent client-side encryption of your files in the cloud.

Download native binaries of Cryptomator on cryptomator.org or clone and build Cryptomator using Maven (instructions below).

Features

  • Works with Dropbox, Google Drive, OneDrive, and any other cloud storage service that synchronizes with a local directory
  • Open Source means: No backdoors, control is better than trust
  • Client-side: No accounts, no data shared with any online service
  • Totally transparent: Just work on the virtual drive as if it were a USB flash drive
  • AES encryption with 256-bit key length
  • Filenames get encrypted, too
  • Use as many vaults in your Dropbox as you want, each having individual passwords

Privacy

  • 256-bit keys (unlimited strength policy bundled with native binaries)
  • Scrypt key derivation
  • Cryptographically secure random numbers for salts, IVs and the masterkey of course
  • Sensitive data is wiped from the heap asap
  • Lightweight: Complexity kills security

Consistency

  • HMAC over file contents to recognize changed ciphertext before decryption
  • I/O operations are transactional and atomic, if the filesystems support it
  • Each file contains all information needed for decryption (except for the key of course), no common metadata means no SPOF

Security Architecture

For more information on the security details visit cryptomator.org.

Building

Dependencies

  • Java 8 + JCE unlimited strength policy files (needed for 256-bit keys)
  • Maven 3
  • Optional: OS-dependent build tools for native packaging (see Windows, OS X, Linux)

Run Maven

cd main
mvn clean install

Contributing to Cryptomator

Please read our contribution guide, if you would like to report a bug, ask a question or help us with coding.

Code of Conduct

Help us keep Cryptomator open and inclusive. Please read and follow our Code of Conduct.

License

Distributed under the MIT X Consortium license. See the LICENSES/MIT-X-Consortium-License.txt file for more info.