![]() ![]() ![]() This means you can convert your existing vaults to Hub vaults and vice versa. Not only that, the recovery key is compatible with Cryptomator’s recovery key. This allows you to access your data in case of disaster. We didn’t stop there and released Cryptomator Hub 1.1.0 with recovery key support. It also helps that Hub is independent of your cloud storage provider, which means we have no access to either the key material or the cloud files. All key material remains locally on the client. Cryptomator Hub doesn’t store unencrypted keys. This is all possible because of the underlying zero-knowledge key management. You can focus on your work and your team. With managed instances, we will take care of deploying and maintaining your Hub instance, while ensuring that your instance is highly available. This includes updating the software, monitoring the instance, and keeping it secure. And if you have the knowledge, you still have to maintain the instance yourself. This requires a lot of knowledge about how to deploy a software container using Kubernetes or Docker Compose. Until now, you could only use the self-hosted version of Hub. Managed instances of Cryptomator Hub are a great way to start using Cryptomator Hub right away without having to deploy and maintain your self-hosted instance. ![]() We are working on automating this process, but we didn’t want to delay the release any longer. Currently, some of the steps we take internally to create a managed Hub instance are still done “manually”. After your request, we will get back to you as soon as possible. □ To get started, you can now request access to a managed instance of Cryptomator Hub. We are happy to announce that managed instances of Cryptomator Hub are now available! □ And we have released Hub 1.1.0 with recovery key support. Cryptomator Hub: Managed – Request Access Now Read more about this in the Cryptomator 1.7.0 blog post. Cryptomator for Android will support both modes of operation. You can continue to use your existing vaults as before, no action is required on your part. 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. 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.Ĭryptomator Lite can be built using the following Docker image and then compared to the corresponding releases: AES-GCM: New Default for Content Encryption 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. Cryptomator Lite: Reproducible Build and F-DroidĪ less obvious change is that we now offer a new flavor: Cryptomator Lite. The most obvious change in this release is the migration to Material 3, which modernizes the user interface. □ In addition to the release notes, we’d like to give you more details about some changes. This release took quite some time, but we finally made it. 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. ![]()
0 Comments
Leave a Reply. |