By continuing you indicate that you have read and agree to our Terms of service and Privacy policy
cryptomator | Multiplatform transparent clientside encryption of your files in the cloud | Encryption library
kandi X-RAY | cryptomator Summary
Support
- cryptomator has a medium active ecosystem.
- It has 7273 star(s) with 613 fork(s). There are 157 watchers for this library.
- There were 4 major release(s) in the last 6 months.
- There are 229 open issues and 1493 have been closed. On average issues are closed in 139 days. There are 5 open pull requests and 0 closed requests.
- It has a neutral sentiment in the developer community.
- The latest version of cryptomator is 1.6.8
Quality
- cryptomator has 0 bugs and 0 code smells.
Security
- cryptomator has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
- cryptomator code analysis shows 0 unresolved vulnerabilities.
- There are 0 security hotspots that need review.
License
- cryptomator is licensed under the GPL-3.0 License. This license is Strong Copyleft.
- Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.
Reuse
- cryptomator releases are available to install and integrate.
- Build file is available. You can build the component from source.
- Installation instructions are not available. Examples and code snippets are available.
- cryptomator saves you 7361 person hours of effort in developing the same functionality from scratch.
- It has 17551 lines of code, 1710 functions and 299 files.
- It has medium code complexity. Code complexity directly impacts maintainability of the code.
kandi has reviewed cryptomator and discovered the below as its top functions. This is intended to give you an instant insight into cryptomator implemented functionality, and help decide if they suit your requirements.
- Migrates the vault .
- Read the settings from the given JSON stream .
- Initialize vault .
- Recursively delete unmounts from a mount point directory .
- Display recovery key .
- Called when a drag is pressed .
- Replaces the input text at the given position .
- Start the Cryptomator instance .
- Creates a crypto file system based on the MasterkeyLoader .
- Initializes the tray icon .
cryptomator Key Features
Works with Dropbox, Google Drive, OneDrive, MEGA, pCloud, 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
Three thousand commits for the security of your data!! :tada:
cryptomator Examples and Code Snippets
Run Maven
mvn clean install
# or mvn clean install -Pwindows
# or mvn clean install -Pmac
# or mvn clean install -Plinux
Community Discussions
Trending Discussions on cryptomator
QUESTION
How to recover from file sync mix-up with TortoiseSVN
Asked 2020-Jul-24 at 05:53I have a file-based TortoiseSVN repo that requires the files to be kept in sync if I need to work across multiple machines (rare... but courtesy of a pandemic, you guessed it).
The inevitable happens: two distinct machines (PC1, PC2) each commit changes, and are assigned the same revision number due to an undetected sync backlog on PC2. Subsequently, PC2 clears the sync backlog, but ends up with a muddled view of the repo:
- PC1 revision history ("Show Log") shows the affected revision has the author and revision comment from PC1, but also files committed from PC2.
PC2 seems totally fine, so the changes submitted on PC1 are re-submitted there. This filters through to PC1 where the revision history shows the latest revision correctly, but the history entry for the previous revision remains muddled as described above.
It seems like a reasonable idea to delete/rename the affected project, and do a fresh checkout. That results in:
- Checksum mismatch for
- Try a 'Cleanup'. If that doesn't work you need to do a fresh checkout
- Cleanup fails; fresh checkout consistently leads to checksum mismatch
So I'm stuck. I guess that something in the .svn folder needs deleting. How can I find out what that something is and remove it without losing either history or affecting other projects from the same repo?
(There are multiple projects/branches in the repo root, and a single .svn file spanning all checkouts from it as far as I can tell. I'm running TortoiseSVN 1.10.5 on Windows 10... and further complicating things by encrypting all the source in the repo using Cryptomator.org)
ANSWER
Answered 2020-Jul-24 at 05:53This answer provided the basis for at least a partial solution... with some careful attention to svn:externals - where there were sub-folders with svn:externals, there were complaints that "the node already exists" (or something to that effect). Every instance like this had to be separately deleted, and the update command run again.
For the most part, existing files from other folders were "versioned" by the SVN update, and not updated. Missing files (or deliberately deleted ones) were replaced. Applying this to all folders/projects led to an error-free result.
But there is one small quirk remaining: the revision history shows the wrong author and log message. However, when I attempt to edit them, the popup dialogs contain the correct author/message. The code changes submitted in error are gone. So there is still some locally duplicated data somewhere, but its effect is cosmetic.
I dare not try to update to the faulty revision...
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install cryptomator
You can use cryptomator like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the cryptomator component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .
Support
DOWNLOAD this Library from
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
over 430 million Knowledge Items
Find more librariesReuse Solution Kits and Libraries Curated by Popular Use Cases
Save this library and start creating your kit
Explore Related Topics
Share this Page
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
over 430 million Knowledge Items
Find more librariesReuse Solution Kits and Libraries Curated by Popular Use Cases
Save this library and start creating your kit