Multi-platform transparent client-side encryption of your files in the cloud
Go to file
2017-06-21 12:56:40 +02:00
3RD PARTY LICENSES Changed license to GPLv3 [ci skip] 2017-06-21 12:56:40 +02:00
main added copyright statement 2017-06-21 11:41:34 +02:00
.gitignore added IntelliJ files to .gitignore 2016-05-16 10:00:39 +02:00
.travis.yml Removed codecov, reporting coverage to codacy 2017-05-12 14:48:15 +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 Update CONTRIBUTING.md 2017-02-10 01:52:13 +01:00
cryptomator.png added issue template, contribution guide, code of conduct [ci skip] 2016-04-05 12:28:36 +02:00
ISSUE_TEMPLATE.md Update ISSUE_TEMPLATE.md 2017-02-10 01:37:21 +01:00
LICENSE.txt Changed license to GPLv3 [ci skip] 2017-06-21 12:56:40 +02:00
README.md removed unused badges [ci skip] 2017-05-12 15:02:57 +02:00

cryptomator

Build Status Coverity Scan Build Status Codacy Badge 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, Nextcloud and any other cloud storage service which 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
  • File names get encrypted
  • Folder structure gets obfuscated
  • 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

Run Maven

cd main
mvn clean install -Prelease

An executable jar file will be created inside main/uber-jar/target.

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.