![]() ![]() With the release of Cryptomator 1.7.0, we will officially deprecate Dokany support.ĭokany, like FUSE, provides a file system interface to mount virtual drives without requiring elevated privileges. If you really need a local drive, you can always change the volume type in the preferences. Accessing the vault as a privileged user is still possible by using the UNC path. The disadvantage is that it cannot be mounted into a directory. This has the advantage of better performance when listing large directories. Windows users may notice that their vault is now mounted as a network drive by default. We’ll have a guide describing this in more detail soon. If you can’t mount your vault at all, it makes your vault accessible via a local-only server using the web standard WebDAV. We have even added an emergency option: The aforementioned “WebDAV (Fallback)”. Otherwise, Cryptomator has a new “Automatic” option and is set up to choose the best suited option for you, and you don’t need to worry about it. For example, on Windows you can select between WinFsp, WinFsp (Local Drive), Dokany, WebDAV (Windows Explorer) and WebDAV (Fallback).īut don’t worry, this selection is only important if you have special requirements for the virtual drive. Now, specialized implementations are offered for each OS. The old implementation basically offered 3 (or 2) options: WebDAV, Dokany, and FUSE. It also resulted in more options for you. ![]() It was a huge development effort, but it resulted in a less complex and easier to maintain architecture under the hood. That’s right, and that’s because we rewrote the entire volume type selection and internal wiring logic. Looking at the screenshot above, you might have noticed: The volume types have changed, too. So, while the File Provider extension is not out of our sight, we are relieved to be able to offer you a stable system integration of your Cryptomator vaults. But since FUSE-T is quite young, support for it is experimental for now. This makes Cryptomator ready for the medium-term future on macOS. It requires a much less deep system integration than macFUSE while offering a similar performance. Fortunately, you, our community, informed us about an alternative: FUSE-T.įUSE-T is a young project that does not rely on deprecated macOS APIs and can be used as a drop-in-replacement for macFUSE. Our proof of concept using Apple’s File Provider framework was not very convincing and would basically require a whole new architecture. Apple has deprecated the OS APIs used by macFUSE since macOS 12.3.įor the past year, we have been desperately searching for an alternative. To make matters worse, macFUSE, which has been the preferred option for at least 3 years, is also on its last legs. Starting with Apple Silicon Macs, it became unusable for some users who reported system freezes. Unfortunately, the WebDAV implementation on macOS is not the most reliable one. ![]() On macOS, Cryptomator can use two different technologies to integrate your vault into the system: macFUSE and WebDAV. Your browser does not support the video tag. Or you can simply drag and drop the files from your vault onto this button. Now, once the vault is unlocked, the encrypted counterpart of any file in the vault can be revealed by clicking on the “Locate Encrypted File” button and selecting a file in the vault. Prior to 1.7.0, you had to guess which encrypted file corresponds to which cleartext file based on the exact timestamps. Sounds complex, but once you remember that Cryptomator encrypts filenames and obfuscates the directory structure ( see our docs), it is easy to understand. Locate Encrypted FileĪs already mentioned, Cryptomator 1.7.0 includes a feature that has been requested for a very long time: Locating the encrypted counterpart of a file. ![]() But putting aside about 3,000 lines of code changes and a 4-month development iteration (not counting work in our libraries), let’s dive into this release to see what you, the user, will get out of it. We are very proud of this release, as it eliminates technical debt, delivers long-awaited features, and prepares Cryptomator Desktop for the future. If you’re subscribed to our releases on GitHub, this is already old news for you: We have released the first beta of the upcoming Cryptomator 1.7.0! It contains a lot of internal changes and a bunch of new features, some of which are almost as old as Cryptomator itself. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |