After releasing updates for iOS and the desktop version of Cryptomator last week, itâs now time for Android! The new 1.10.3 update is now available, providing even stronger protection for your data. Letâs take a closer look at the key improvements.
Key Updates at a Glance
Migrating vault passwords to GCM
Thai as a new language option
What’s New?
Migrating Vault Passwords to GCM
Weâve improved the encryption for vault passwords and cloud credentials! From now on, weâre using AES-256 GCM instead of AES-256 CBC to provide even stronger protection. Passwords and credentials are still securely stored in the Android Keystore, and your data remains protected in internal storage thanks to Androidâs sandbox model.
With the app update, existing cloud credentials and vault passwords will automatically migrate to the new format. You may opt out of migrating vault passwords, but if you do, the passwords will be deleted from the app for security reasons.
New Language: Thai
Another exciting update: The Cryptomator app is now available in Thai! Weâre thrilled to make our app accessible to even more users around the world and grow our community. This new language option makes it easier and more comfortable for Thai users to enjoy Cryptomator.
A big thank you goes out to our dedicated community for helping us optimize Cryptomator for more countries and languages. If youâd like to contribute to translations, feel free to join us here: https://translate.cryptomator.org.
Conclusion
While the 1.10.3 update for Android might seem small at first glance, the improvements are crucial for the protection of your data. Even though the previous implementation was already secure within the Android ecosystem, weâve enhanced it to meet the latest security standards.
We appreciate your ongoing feedback and support. Try out the new version and let us know what you think!
Current Issue with Google Drive Connection in Cryptomator for Android and iOS
Update 2024-08-22
Weâre thrilled to announce that the issue with Google Drive connectivity in Cryptomator for Android and iOS has been fully resolved. Google has accepted the Letter of Approval from our auditing company.
As a result, Google Drive access has been restored, and you can now use Cryptomator as usual without any restrictions.
We deeply appreciate your patience and understanding throughout this period.
Update 2024-08-19
Weâre pleased to share a positive update regarding the ongoing issue with Google Drive connectivity in Cryptomator for Android and iOS.
We have just received confirmation from the auditing company that the Letter of Approval (LOA) is set to be submitted to Google within the next 1-2 business days. This is the final step in the verification process, and once submitted, we anticipate that Google Drive access will be restored shortly thereafter.
We are cautiously optimistic that full functionality will be available again within the next few days. We sincerely apologize for the inconvenience this has caused and appreciate your continued patience and understanding as we work through this final stage.
Hello Community!
We would like to inform you about a current issue that some of you may be experiencing while using our Cryptomator apps for Android and iOS. It involves difficulties in connecting to Google Drive that have arisen in the past few days. Here, you will find all the details and updates on our progress in resolving the issue.
What Happened?
Google recently introduced significant changes to its app verification system. These changes particularly affect how apps access services like Google Drive. As a result of this update, you may encounter an error message when trying to connect Google Drive with Cryptomator, stating that Cryptomator is blocked because it is an “unverified app”.
Why Is This Issue Occurring?
Google has substantially tightened the requirements for app verification, especially for apps that access sensitive user data. This not only affects Cryptomator but potentially all apps that integrate with Google services. The aim of these changes is to enhance user security and protect their data. However, as a consequence, apps that have not yet fully adapted to the new system may be temporarily blocked.
What Are We Doing to Resolve the Issue?
We are fully aware of the problem and are working diligently to find a solution. Our team is in close contact with Google to complete the necessary verification processes and re-certify Cryptomator as a trusted app. Unfortunately, this task is more complex than initially anticipated. Google’s new requirements necessitate additional adjustments to our app, which must be carefully implemented and tested.
We want to emphasize that the security of your data is our top priority. Therefore, we are taking the time to thoroughly implement these changes to ensure that Cryptomator remains a secure and reliable solution for your encrypted data.
What Can You Do?
We understand that this issue is frustrating for many of you, and we sincerely apologize for the inconvenience. In the meantime, there are a few things you can do to avoid interrupting your workflow:
Use Alternative Cloud Services: If you cannot use Google Drive at the moment, you have the option to integrate alternative cloud services like Dropbox, OneDrive, or WebDAV-based services in Cryptomator.
Local Decryption: You can still decrypt your encrypted vaults using the desktop application. If the vault is not that large, you can also download it to your mobile device and decrypt it locally.
Monitor Updates: We will keep you regularly informed about the progress of our work. As soon as the issue is resolved, we will promptly notify you with the corresponding updates. Keep an eye on our social media accounts on X and Mastodon for updates.
Outlook
We are confident that we will be able to provide a solution soon. Our goal is to restore full functionality to Cryptomator as quickly as possible. We greatly appreciate your patience and understanding during this time.
Once again, thank you for your support and trust in Cryptomator. We are working tirelessly to provide you with the best possible experience with our app, and we will keep you informed as soon as there are any updates.
Best regards,
The Cryptomator Team
FAQ: Google OAuth Issues in Cryptomator for Android and iOS
Q1: What is the issue with Google Drive and Cryptomator for Android and iOS? A1: Users are experiencing issues with Google blocking access to your files when using Cryptomator for Android and iOS during the sign-in process.
Q2: How can I access my files? Is there a workaround? A2: You can always access your files on your Desktop computer or by copying your vault from your Google Drive to your phone’s harddrive and then using Cryptomator for Android and iOS to access them locally.
Q3: Are my files safe? Is my account safe? A3: Yes. Your files and account both are safe and at no risk of being deleted or accessed by malicious actors. They are not any less safe than they were a week ago.
Also your files are still encrypted.
Q4: Is there a problem with my Google account? A4: No. This is not a problem with your Google account and this should affect all users of Cryptomator for Android and iOS and Google Drive.
Q5: Is Cryptomator for Android and iOS safe? A5: Yes. Cryptomator for Android is safe and we are currently not aware of any security issues.
Also see Q7.
Q6: Which “sensitive info” is Cryptomator for Android and iOS trying to access? A6: To allow access to the files you have stored in Google Drive and to enable the associated functionality, the Cryptomator app needs access to your Google Drive.
Even if the message from Google sounds scary, this is nothing new and nothing to worry about.
Also see Q7.
Q7: Why is this happening? Why is Google blocking Cryptomator for Android and iOS? A7: To enable access to your files stored in Google Drive, Cryptomator needs both your permission and Google’s consent. Google has recently adopted newer and stricter security policies that we must adhere to in order to continue to provide access to your Google Drive in the app. If we don’t prove to Google in time that we comply with these guidelines, access will be blocked, which is what is happening right now. We are currently in the middle of this verification process to regain access, but this is quite time-consuming and labor-intensive, all of which has led to this situation.
Q8: What about Cryptomator for Desktop? A8: The affected functionality is not offered by Cryptomator for Desktop, so there currently is no problem there.
Cryptomator 1.8.0 for Android
As you may have already noticed, we released Cryptomator 1.8.0 for Android last month! It contains a lot of internal changes, a bunch of new features, and some bug fixes.
This release took quite some time, but we finally made it. 🎉 In addition to the release notes, we’d like to give you more details about some changes.
Material 3 Design
The most obvious change in this release is the migration to Material 3, which modernizes the user interface.
Cryptomator Lite: Reproducible Build and F-Droid
A less obvious change is that we now offer a new flavor: Cryptomator Lite.
This version is built using a reproducible build technique, which has two advantages: You as a user can verify that the published source code matches the published binary, which in turn means that we didn’t and couldn’t add anything during build time.
The other advantage is that this technique allows us to publish our app to stores like the main F-Droid repository, but sign it with our keys, which means we still have control over the signing keys.
Starting with Cryptomator 1.8.0 for Android, we will follow our Desktop application: All newly created vaults will use AES-GCM instead of AES-CTR+HMAC for file content encryption.
You can continue to use your existing vaults as before, no action is required on your part. Cryptomator for Android will support both modes of operation.
There have been a lot of changes in the past year. With this roadmap, we want to give you an overview of what has changed in Cryptomator and what you can look forward to in the coming months.
iOS Version
At the end of last year, we were finally able to introduce our new iOS app. One of the main features is the full integration with Apple’s own Files app. We also made it possible to offer you a “freemium” version of the app. If you want to know even more about the new features, check out this blog post. Since then, we’ve been working on bringing you more features through several updates, such as the auto-lock feature that came with version 2.1.0. With the just released version 2.2.0, we integrated pCloud and added support for shortcuts in Google Drive.
We have a lot more planned for the app in the coming months. We will integrate Cryptomator into Shortcuts so that automation processes such as “auto photo upload” are possible. We also plan to integrate S3, as we did with our Android app.
Android Version
Over the past few months, we have been working on increasing the compatibility of Cryptomator. This includes the fact that we now support pCloud, S3, and Vault Format 8. Thanks again Manuel (mjenny on GitHub) for contributing support for pCloud and S3. Also, Cryptomator can now be installed and updated via F-Droid. Vaults in Google Drive can now be used via shortcuts in locations outside of “My Drive”. This works in “Shared with Me”, “My Computer”, and “My Drive” for example. With OneDrive, it is possible to use multiple accounts at the same time. We will make this feature available for Dropbox and Google Drive in the future. In addition, a “real” auto photo upload is available in the Android version, meaning new pictures and videos are now uploaded not only after unlocking the vault, but directly when it is unlocked.
In the coming months, we will switch the Android app to a freemium model, as we did with iOS, and continue to work on the long-awaited document provider.
Desktop Version
With version 1.6.0 announced in the last roadmap, we introduced Vault Format 8 for our Desktop version. You can read more about it here. For better usability, we have introduced error codes and a knowledge base of those, where you can look up solutions for the issue youâve encountered. We also introduced an auto-lock feature that automatically locks the vaults after a self-defined inactivity time as well as a plugin API. The first plugin for Cryptomator is the KeePassXC plugin via an open-source contribution by Ralph (purejava on GitHub). Furthermore, we improved our build systems so that applications/installers for all operating systems are automatically built and signed (instead of manually).
Two years ago, one might remember that we announced to focus our efforts on Flatpak distribution. However, that didnât go as planned and progress on it came to a halt⌠until recently. Our regular open-source contributor Ralph (purejava on GitHub) once again came to our rescue. And we actually did it! Cryptomator is now available on Flathub as a Flatpak app. Again, huge thanks to Ralph for his amazing contribution!
For the Desktop version of Cryptomator, we have some major topics coming up in the near future. On the one hand, we are working on a major FUSE refactoring. Among other things, this is necessary to be able to offer ARM64 support on Windows and Linux as well. On Apple Silicon Macs, we have already supported this for a few releases. On the other hand, we want to address the open issues related to extended attributes. More precisely, we are talking about additional file attributes that enable tagging and fix compatibility issues. Of course, these attributes will be encrypted just like the filename.
If you read this far, weâd like to share a secret with you. We are currently working on Cryptomator Hub. Thatâs it for now but youâll definitely hear more about it this year.
Update on the Document Provider Development
Hey Community,
From time to time, we need to adjust our schedule for certain features. We are well aware that the Document Provider is the most-requested feature of the Android app, but despite this fact, we need to temporarily shift our attention to other tasks within this project. This blog post you’re reading right now is to keep you, our community, updated and inform you that we are unable to stick to our original plan. Unfortunately, this means that any further development of the Document Provider feature needs to be postponed to the end of this year.
The Document Provider Feature
As users of our Android app, you know how cumbersome sometimes the work with it is: You open your favourite notes app to quickly jot something down, then notice that you cannot open your to-do list from the app because you store it encrypted with Cryptomator. So you sigh, open the Cryptomator app, unlock your vault, navigate to the to-do list file and open it with the aforementioned notes app. Definitely not the optimal workflow.
We always strive to provide the same features across all our supported platforms. One of these is a user-friendly integration of the vault into the running OS to easily access content of unlocked vaults. For the desktop systems, this feature was always present and recently we added it in our new iOS app. The last OS, where it is missing is Android. And the way to resolve this, is implementing a Document Provider for our Android app.
The Document Provider feature creates a virtual access point to an unlocked vault, with the consequence that you can conveniently browse and access a vaultâs content via the standard file browser. Also, any app which supports browsing through Document Providers can directly load files from your unlocked vault without the need to go via Cryptomatorâs app GUI.
As you can see, the issue is already quite old and got over the time a countable amount of comments. After publishing the source code of the app at the end of 2020, our plan was to work on this important feature.
From the technical side, we already determined the parts of code needed to be edited, developed a concept and built a proof of concept (see the linked ticket). The next step would be to actually implement it including rigorous testing.
Unfortunately, we determined that integrating Document Provider into the existing app would require major architectural changes, therefore requiring a lot of time and resources. We have exciting plans with Cryptomator after our next major release with version 1.6.0 so that we have to delay the development of the Document Provider integration to the end of 2021.
Meanwhile, maybe you, our community can help us out.
Call for Contributions
Cryptomator for Desktop was always open source. Cryptomator for iOS and Android are now open source as well. And as such, we also rely on our community to receive feedback, distribute the app and improve its functionality.
So, we are always very excited about contributions and are happy to assist, especially when it comes to the Document Provider. 😉
Cryptomator Roadmap Early 2021
Development on Cryptomator 1.5.x is coming to an end and we are now working on the next major version 1.6.x. Read more about it in this roadmap!
State of the Desktop App
The update to version 1.6.0 is just around the corner! The release will mainly contain some invisible changes that will allow us to add new features in a timely manner. One of the main points here is to implement a new vault format (Vault Format 8). It makes the integration of other authentication methods in the future possible, for example to enable 2FA.
Another feature is the integration of a sanitizer. Until now, a separate program was needed to check the state of your vault and to execute cleanup and restore commands. In the future, this will be possible directly in the Cryptomator user interface.
In addition, there is now a prototype for the distribution of Cryptomator as a Microsoft Software Installation (.msi), but the implementation still has alpha character. Furthermore, we have updated Cryptomator to JDK 16 with the latest version 1.5.14, which brings some upstream fixes. Unfortunately, we could not make any progress with regard to Flatpak.
State of the Android App
As you might have noticed in our blog, we finally published the source code of the app! Apart from that, vault format 8 is also a big topic in our development here.
Since the update to version 1.5.14 (currently still in a beta version), pCloud is natively supported by Cryptomator. Many thanks to Manu for his open source contribution! Another small change is that since the update 1.5.13, it is possible to sort the vault list and thus get a better overview of the vaults.
But that’s not all we have planned for the Android app! We are happy to release Cryptomator on F-Droid soon. Also, we hope to be able to include more clouds soon and enable access to content of the vault via third-party apps with a “document provider”.
State of the iOS App
With the introduction of vault format 8, the “old” iOS app will probably get its last major update to version 1.6.0.
Meanwhile, work on the “new” iOS app continues. As announced in the last roadmap, the iOS app will be fully integrated into the Files app. We are already very far along. Nevertheless, we still have some work to do, as we want to offer some features like dark mode or support for multiple accounts from the same cloud provider right from the start.
We can’t promise you an exact release date yet, but we hope we will release a first beta version via TestFlight in the summer.
Open Source: Cryptomator for Android
We announced it last month and now we are ready⌠our gift to the community for the holidays: Cryptomator for Android is now fully open-source! Check out the repository here: https://github.com/cryptomator/android
There will definitely be a transition phase and learning curve for us to fine-tune the repository and coordinate open-source contributions but it shouldn’t be too far off the “main” repository Cryptomator for Windows, macOS, and Linux, which was open-source from the beginning.
We are looking forward to your contributions and are very grateful to you and the whole community that made this step possible. To support the ongoing open-source development of Cryptomator, consider donating or sponsoring. ❤️
And what about Cryptomator for iOS? To quote from our “Roadmap Late 2020”:
We won’t open-source the current app anymore because we’d like to look forward. The new app is written with open-sourcing it in mind but it will still take some time until we can release anything.
Happy holidays and a happy new year! 🎁
Cryptomator Roadmap Late 2020
We recently released Cryptomator 1.5.10 for Windows, macOS, and Linux with many new features and bugfixes. Well, actually the changes were in 1.5.9 but we followed it up with a hotfix release. 😁 With the (crazy) year nearing its end, we’d like to give you some insight to our roadmap across all platforms for the upcoming months!
State of the Desktop App
With the redesign and full rewrite of the UI in 1.5.0, we established a good foundation for adding further features. There was one former feature that didn’t make the cut though, which is now back with the latest version: Vault Statistics. 🎉
We didn’t stop there! Vault passwords can now also be stored in KWallet on Linux. Huge thanks to Ralph Plawetzki (purejava on GitHub) for his contribution! And last but not least, it is now possible to mount the vault via FUSE on Windows. This is still a beta feature! In order to try it, WinFSP needs to be installed. We’d love to hear your feedback on this!
On the distribution front, we didn’t quite meet our expectations. So far, we’ve been struggling with Flatpak as we just can’t convince its sandbox to properly support FUSE drives. But we’re not giving up on this!
Behind the UI, we introduced the integrations-api alongside implementations for each OS. It’s a new way for Cryptomator to include native (also OS-specific) functionalities. Now easier than ever, you can implement native functions. So grab your keyboard and start hacking! 😁 With this change, we archived the old native-functions repository. 👋
What’s next? Our plan is to move on to 1.6.x. First of all, we want to integrate Sanitizer, so you can check your vault health and run cleanup and recovery tasks right within the Cryptomator UI. Furthermore, by decoupling the key derivation from the vault encryption, we plan to give you more options for authentication, including third-party password storage, 2FA, and multi-user access using individual passwords.
Looking forward, we have some exciting news about our Android app! The project is in the perfect situation to fulfill the two biggest wishes of the community:
Open Source: Publishing the source code of the app.
Document Provider: Accessing the content of the vault using third-party apps.
You heard that right, we are going to open-source Cryptomator for Android! The fact that the app is open-core had its legitimate reasons but we are now fully confident that we can open-source the app without compromises. We are working hard to publish the complete source code within a few weeks.
After that, the highly anticipated Document Provider feature will be on our roadmap.
State of the iOS App
What’s up with Cryptomator for iOS? For the last 6-7 months, we have been hard at work on a completely new app written in Swift. Our first efforts can already be seen in our new open-source libraries for Swift: cryptolib-swift and cloud-access-swift.
What will be so special about the rewrite? Cryptomator will be fully integrated into the Files app. This comes with many benefits like thumbnails, support for third-party apps that can edit files directly inside the vault, and many more! But that also means, there won’t be a “custom” file browser inside the app anymore. Integration into the Files app is one of the most requested features of the community.
What about open source? We won’t open-source the current app anymore because we’d like to look forward. The new app is written with open-sourcing it in mind but it will still take some time until we can release anything.
We’ll definitely do extensive testing via TestFlight in the next year. Stay tuned for that!
Cryptomator for Android for Us Paranoids
This blog post is aimed towards the paranoid Cryptomator power users among us and describes how to fully establish a relationship of trust with Cryptomator for Android.
When it comes to our desktop application, we claim that you should in fact not trust us but you (or at least many developers) can instead inspect what Cryptomator is doing. For our mobile apps, this is only half the truth, frankly. While the encryption code is fully open-source, the UI and cloud access code isn’t (yet 😉).
If you count yourself as one of the more paranoid users, who prefer to compile everything yourselves, you might ask the legitimate question: How can you check the current, open-core app for backdoors?
A backdoor usually requires communication with an external server. If vaults are only opened from the device’s file system, the Cryptomator app does not require an internet connection. Alternatively, the vault can be synchronized bidirectionally to the file system of the smartphone with a third-party application such as Syncthing.
Using this setup, the Cryptomator app can have its internet access revoked using the Android operating system features, which prevents the app from sending or receiving any data to or from the internet.
Thus, even if there ever was a backdoor in Cryptomator for Android, it would not be possible for the intercepted data to leave the smartphone. This is ensured by the operating system.
Cryptomator 1.5.0 Release
Cryptomator has been redesigned and comes with a new dark mode. It is not simply a redesign, it was a full rewrite of the UI. During the rewrite, a whole new code structure was planned which makes it easier to extend the application in the future. One goal of the redesign was to make the onboarding process easier for users who don’t feel too comfortable with encryption software. Usability tests helped designing the workflows and understanding common misconceptions. Besides the redesign, the new vault format 7 increases compatibility with some cloud services and at the same time reduces the complexity for certain I/O operations.
To support the ongoing open-source development of Cryptomator, consider buying a donation key, which unlocks the new dark mode. ❤️ Detailed release notes for the desktop app are available on GitHub.
As you might have noticed, this website is also shining in a completely new design. ✨
Cryptomator for iOS & Android
New updates for iOS and Android have been released as well. To celebrate the release, our mobile apps are 40% off until April 23! 🤖
Between all the work on Cryptomator, we need to remind ourselves to not forget about our regular updates post. While most of you have already noticed that we’re approaching a new major release of Cryptomator, I think it is time to inform you where we’re currently standing and what our roadmap looks like.
State of our Desktop Application
We plan to release 1.5.0 within Q1 2020. In our currently running beta (huge shout-outs to all the helpful test feedback), we have already sorted out several problems and feel confident to deliver outstanding quality.
While we have already discussed upcoming changes to what we call the vault format (i.e. the layout of the encrypted files and directory) to increase compatibility with some cloud services and at the same time reduce the complexity for certain I/O operations, the far more obvious change affects the GUI:
We did not simply redesign our UI, we did a full rewrite of it. Nearly every single line of code that was involved in Cryptomator 1.4.x has been deleted. Why would you do something like this? Well, the application grew over time. Cryptomator has been started more than six years ago and some concepts weren’t established back then that make development easier today. During the rewrite, we planned a whole new code structure which makes it easier to extend the application in the future and at the same time have new developers understand what parts of the code is responsible for what dialog in the software.
One goal of the redesign was to make the onboarding process easier for users who don’t feel too comfortable with encryption software. We attended (and organized) some usability tests in our vicinity and saw how first-time users reacted to the vault creation process. This helped us to design the workflows and understand common misconceptions.
State of the Android App
Not worth mentioning is that the Android app in 1.5.0 will support vault format 7. In the Android app, we focused on implementing new features and improving stability:
Already opened files are cached on the smartphone. When reopened and if the file has not changed in the cloud, the file is loaded from the local file system, which leads to a huge performance improvement.
Fixed and improved auto photo upload e.g., after device reboot or on Android 10 under certain conditions the upload didnât work
We added an option to lock a vault immediately when Cryptomator is closed or in background
Last but not least, we’ve put a lot of work into a new license store that will enable us to provide an alternative way of distributing our Android app, as we have a lot of requests from users who prefer not to use Google services such as the Play Store
State of the iOS App
The iOS app will also support vault format 7, obviously. There are some further fixes and improvements under the hood, but no new features. It already supports caching and it you can even buy it without using the Google Play Store. 😉
What is missing for the final release of 1.5.0?
While at the time of writing this, there are only few missing features planned for 1.5.0 (such as vault recovery) and only some final polishing is required from our side, we want to make sure our mobile apps and also third party apps such as Cyberduck are ready to deal with the new vault format, too. For some bugs scheduled for 1.5.0 (such as this one), we’re currently waiting for an upstream fix.
Simultaneously, we’re preparing new documentation pages for 1.5.0 as well as a new website with a new FAQ section and we integrate new translations added by our great community on a regular basis.
What’s up next?
Our first priority right after 1.5.0 is to migrate from Java 11 to Java 14. Java 14 includes a long-awaited new tool that is required for our packaging. We’re currently using a workaround that prevents us from upgrading to the latest bundled JRE. This is a small change that will probably be shipped right with 1.5.1. However, we didn’t want to dig up new holes right before 1.5.0 and decided to postpone this to 1.5.1.
Next, we want to focus on Flatpak. We ditched .deb and .rpm files some time ago and replaced them with AppImages. We also really like how the Flatpak ecosystem is gaining traction and is supported natively by a steadily increasing number of distributions. So far, we didn’t get Cryptomator working due to the complexity behind the file system mounts. But after we’ve finished 1.5.0, we hope to be able to put some more attention to this and solve this to ship Cryptomator as a Flatpak soon.
In the Android app, the next big feature will be accessing files of a Cryptomator vault inside other apps using a DocumentProvider. For example, a file explorer will be able to access the content of the vault in this way. As well as smaller features like recursive upload of folders to the vault are planned.
Cryptomator Roadmap Mid 2019
We would like to take a more regular look at our roadmap to publicly document the past, present, and future developments of Cryptomator. Unlike before, we’re also going to have a look at the roadmaps of our mobile apps.
Desktop
In the desktop area, we are currently pursuing two different branches: On the one hand we are striving for feature completion of 1.4.x, with 1.4.12 already available as a release candidate. It will finally allow Linux users to store their password in the system and include the much desired “Custom Mount Flags” feature.
Save password in system (Linux): For a long time, you could only store your vault’s password in the system under macOS and Windows. Through a community contribution, this is now finally also possible under (some) Linux systems. 😄 The existence of GNOME Keyring or another keychain via Secret Service API is required. Many thanks to Ralph Plawetzki (purejava on GitHub) and Sebastian Wiesendahl (swiesend on GitHub) for the implementation!
Custom Mount Flags: Cryptomator uses default options to mount a drive (both for Dokany and FUSE) that we chose for security or performance reasons. However, this leads to limited functionality in some cases and users who want to set their own options can now change them. Be aware: Use at your own risk!
On the other hand the implementation of 1.5.0 has already started. For 1.5.0, as announced, we want to fully concentrate on the redesign of the user interface and improve the internal processing of Cryptomator, because like many open-source projects it has grown organically over time and therefore needs a good refactoring. 😉
iOS
After the release of Cryptomator 1.4.0 for iOS with built-in cache functionality, which on the one hand avoids repeated downloading of files and on the other hand allows (limited) offline access, the work on Cryptomator 1.5.0 for iOS has started.
The main focus will be the integration into the Files app of iOS. The first step will be the expansion of our Document Provider which is going to be extended by the methods “Open” and “Move”. This will make a direct access to files within a Cryptomator vault from other apps possible without having to copy them back and forth.
Android
Cryptomator 1.4.0 for Android is currently being finalized with the following features, which can already be tested in a beta version:
Automatic photo upload: After activation, all images created on the smartphone will be uploaded the next time the selected vault is unlocked.
Make files writable by third-party apps: Files that are opened can be edited in third-party apps. When you finish the editing process by saving and returning to the Cryptomator app, the changes are transferred to the cloud.
We are considering these features for future versions:
LRU Cache: To save network traffic, certain server responses are cached to avoid repeated downloading, for example of unmodified images from the cloud.
Support for Google Team Drives: Access to vaults located in Google Team Drive should be made possible.
Distribution of the app outside of Google Play: Cryptomator for Android should also be available from alternative sources. We are thinking about setting up a licensing system, through which a license could be purchased directly.
Unlocking with system password: You should be able to use the system password of the smartphone to open vaults. (Similar to unlocking with a fingerprint.)
Access to files via DocumentProvider: Access to a Cryptomator vault inside other apps should be made possible via a DocumentProvider. For example, a file explorer would then be able to access the vault in this way.
Upload of directories (recursive): The download of whole folders already works, the upload including all subfolders is not possible yet.
Cryptomator 1.0 for Android Release
Today, we are glad to announce the release of Cryptomator 1.0 for Android. 🎉 Finally, you can protect your cloud files also on Android devices. The app is naturally fully compatible to the desktop and iOS versions of Cryptomator.
We have worked extensively during the last year to ensure the app’s security and usability. Thanks to your feedback and the experiences of more than 10,000 beta testers, the Android app has finally reached the level of maturity that fulfills Cryptomator’s high standards.
In version 1.0 for Android, the app is compatible with Dropbox, Google Drive, OneDrive, and WebDAV-based providers. You can also create vaults in Android’s local storage and, e.g., sync them with third-party apps. The app is available for $4.99 in the Google Play Store.
Added âlock all vaultsâ option to the auto-lock notification
Improved performance of the cloud login process
Removed internet connection requirement for local storage
Fixed display problem when logging in to OneDrive
Translated app into Spanish
Increased Android requirement to version 4.3
Fixed several smaller bugs and problems
Cryptomator 1.3.0 Release
We’ve completely rewritten Cryptomator. Its core components are now modularized to CryptoLib, CryptoFS, and WebDAV-NIO-Adapter. A complete list of closed issues is available here.
Improvements
Auto-Unlock!!! 🎉 (#40) We finally implemented the most-wished feature. Still experimental and will be completed by autostart (optionally hidden) in future versions
Dropped SHA-1 signatures in Windows Authenticode code signing
Dropped official Windows Vista support
Dropped official Ubuntu Vivid and Wily support
Technical Details on Windows Mounting
After we have fixed #431, we noticed various issues on Windows. We tried hosting the virtual drive via localhost, 127.0.0.1, and ::1 but every host has its own issue: Sometimes access to the virtual drive was extremely slow, sometimes Windows showed unnecessary security warnings (#529), and sometimes Office didn’t properly work (#512). That’s why the Windows installer for Cryptomator now writes the new host cryptomator-vault (which is mapped to 127.0.0.1) into the hosts file. Weirdly enough, with that new host, all problems seem to be gone. Even though we don’t quite understand why binding an IP has such a big impact, we just hope that we finally found a good solution!
Under-The-Hood Improvements
We’d like to highlight some improvements that we were able to make under-the-hood: Faster build times, high test coverage for our crypto libraries, and more!
This version will be released shortly and might be the last major beta version. We are now in preparations for releasing Cryptomator 1.0.0 for Android. Looking forward to a great first final release!
Cryptomator for Android 0.1 Beta
We’ve finally released the first beta version of Cryptomator for Android after almost 6 months of development. It’s a completely new and native app. In this process, we outsourced the cryptographic code from our main project, which is now available as CryptoLib.
You’re welcome to test the beta version. Follow this link for more information. Version 0.1 is by far not feature-complete and has known issues, but we’re of course open for feature requests, suggestions, and obviously bug reports.
You can send us feedback on GitHub. We’ve created a repository just for collecting Android issues. Please review and follow our contribution guidelines.
Thank you all for your patience! We know some of you have been already waiting for an Android app of Cryptomator for many months. We’re looking forward to your feedback! 😄
What’s next?
Version 0.2: We’re going to fix some critical/major bugs first, don’t expect too many new features.
After that we’ll most likely successively add support for Google Drive, OneDrive, and WebDAV.
Our goal is to add the functionality equal to the iOS app for the final version.
