Multi-platform transparent client-side encryption of your files in the cloud
Go to file
2018-04-07 00:42:08 +02:00
.github moved issue templates to .github directory 2018-04-07 00:42:08 +02:00
3RD PARTY LICENSES Changed license to GPLv3 [ci skip] 2017-06-21 12:56:40 +02:00
main updated dependencies 2018-04-06 16:29:40 +02:00
.gitignore Forcing RMI to use sotimeout set by socket factory 2017-11-16 15:29:11 +01:00
.travis.yml Merge tag '1.3.4' into develop 2018-03-29 12:58:53 +02:00
cryptomator.png added issue template, contribution guide, code of conduct [ci skip] 2016-04-05 12:28:36 +02:00
LICENSE.txt Changed license to GPLv3 [ci skip] 2017-06-21 12:56:40 +02:00
README.md Update README.md 2018-03-13 12:13:16 +01:00
SUPPORT.md updated readme [ci skip] 2017-07-21 15:50:27 +02:00

cryptomator

Build Status Known Vulnerabilities Codacy Badge Twitter POEditor Latest Release Community

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, ownCloud, 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
  • One thousand commits for the security of your data!! 🎉

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.

License

This project is dual-licensed under the GPLv3 for FOSS projects as well as a commercial license for independent software vendors and resellers. If you want to modify this application under different conditions, feel free to contact our support team.