-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
34a8e36
commit 7f285a8
Showing
73 changed files
with
2,498 additions
and
2,998 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -11,9 +11,44 @@ | |
<title>Cryptomator Blog</title> | ||
<link>https://cryptomator.org/categories/</link> | ||
</image> | ||
<lastBuildDate>Tue, 22 Oct 2024 10:15:13 +0000</lastBuildDate> | ||
<lastBuildDate>Wed, 23 Oct 2024 10:34:59 +0000</lastBuildDate> | ||
<generator>Hugo</generator> | ||
|
||
<item> | ||
<title>Cryptomator 2.6.3 for iOS: New Features and Bug Fixes</title> | ||
<description><p>We&rsquo;re excited to announce the release of Cryptomator iOS version 2.6.3! This update mainly contains important bug fixes to improve your user experience. However, you can also look forward to a small new feature. Let&rsquo;s take a look at everything in detail!</p> | ||
<h2 id="key-updates-at-a-glance">Key Updates at a Glance</h2> | ||
<ul> | ||
<li>New variants of app icons.</li> | ||
<li>More comprehensible error dialog introduced when re-authentication is required.</li> | ||
<li>Missing lock symbol restored.</li> | ||
</ul> | ||
<figure class="text-center"> | ||
<a href="https://apps.apple.com/us/app/cryptomator/id1560822163" target="_blank" rel="noopener"> | ||
<img class="inline-block rounded" src="https://cryptomator.org/img/blog/ios-2.6.3.png" srcset="https://cryptomator.org/img/blog/ios-2.6.3.png 1x, https://cryptomator.org/img/blog/[email protected] 2x" alt="New variants of app icons in Cryptomator 2.6.3 for iOS" /> | ||
</a> | ||
</figure> | ||
<h2 id="whats-new">What&rsquo;s New?</h2> | ||
<h3 id="new-app-icons">New App Icons</h3> | ||
<p>In this update, we&rsquo;ve added new app icon variants for dark mode and tinted mode, offering a more personalized look depending on your preferences and environment. Whether you prefer a sleek dark interface or a touch of color, Cryptomator now adapts to your style!</p> | ||
<h2 id="bug-fixes">Bug Fixes</h2> | ||
<h3 id="clearer-error-screen-for-re-authentication">Clearer Error Screen for Re-Authentication</h3> | ||
<p>Additionally, we&rsquo;ve made a significant improvement to the error screen. If access to a vault is denied due to authentication issues, the app now provides a clearer message that re-authentication is required in the main app.</p> | ||
<h3 id="lock-icon-in-vault-list">Lock Icon in Vault List</h3> | ||
<p>Lastly, we&rsquo;ve addressed an issue many of you reported: the missing lock icon in the vaults list. With this bug fix, you can now quickly see which vaults are unlocked at a glance and easily lock them again using the lock icon.</p> | ||
<h2 id="final-thoughts">Final Thoughts</h2> | ||
<p>We&rsquo;re always working to enhance your privacy and security, and this update is no exception! As always, we look forward to your feedback and continue to thank you for your ongoing trust and support.</p> | ||
</description> | ||
<pubDate>Wed, 23 Oct 2024 00:00:00 +0000</pubDate> | ||
<link>https://cryptomator.org/blog/2024/10/23/ios-2.6.3/</link> | ||
<guid isPermaLink="true">https://cryptomator.org/blog/2024/10/23/ios-2.6.3/</guid> | ||
|
||
<category>cryptomator</category> | ||
|
||
<category>ios</category> | ||
|
||
</item> | ||
|
||
<item> | ||
<title>Cryptomator 1.10.3 for Android: What’s New?</title> | ||
<description><p>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.</p> | ||
|
@@ -386,69 +421,5 @@ Also see <strong>Q7.</strong></p> | |
|
||
</item> | ||
|
||
<item> | ||
<title>Cryptomator 1.7.0: What You Need to Know</title> | ||
<description><p>If you&rsquo;re subscribed to our <a href="https://github.com/cryptomator/cryptomator/releases">releases on GitHub</a>, this is already old news for you: We have released the <a href="https://github.com/cryptomator/cryptomator/releases/tag/1.7.0-beta1">first beta</a> 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.</p> | ||
<p>We are very proud of this release, as it eliminates technical debt, delivers long-awaited features, and prepares Cryptomator Desktop for the future. But putting aside about 3,000 lines of code changes and a 4-month development iteration (not counting work in our libraries), let&rsquo;s dive into this release to see what you, the user, will get out of it.</p> | ||
<figure class="text-center"> | ||
<img class="inline-block rounded" src="https://cryptomator.org/img/blog/cryptomator-1-7-0.png" srcset="https://cryptomator.org/img/blog/cryptomator-1-7-0.png 1x, https://cryptomator.org/img/blog/[email protected] 2x" alt="Cryptomator 1.7.0 Release" /> | ||
</figure> | ||
<h2 id="locate-encrypted-file">Locate Encrypted File</h2> | ||
<p>As 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. Sounds complex, but once you remember that Cryptomator encrypts filenames and obfuscates the directory structure (<a href="https://docs.cryptomator.org/en/latest/security/architecture/#filename-encryption">see our docs</a>), it is easy to understand.</p> | ||
<p>Prior to 1.7.0, you had to guess which encrypted file corresponds to which cleartext file based on the exact timestamps. Now, once the vault is unlocked, the encrypted counterpart of any file in the vault can be revealed by clicking on the &ldquo;Locate Encrypted File&rdquo; button and selecting a file in the vault. Or you can simply drag and drop the files from your vault onto this button. See for yourself in this short video:</p> | ||
<video class="rounded" autoplay loop muted playsinline> | ||
<source src="https://static.cryptomator.org/blog/locate-encrypted-file.mov" type="video/mp4"> | ||
Your browser does not support the video tag. | ||
</video> | ||
<h2 id="experimental-support-for-fuse-t">Experimental Support for FUSE-T</h2> | ||
<p>On macOS, Cryptomator can use two different technologies to integrate your vault into the system: macFUSE and WebDAV. Unfortunately, the WebDAV implementation on macOS is not the most reliable one. Starting with Apple Silicon Macs, it became unusable for some users who reported system freezes. To make matters worse, macFUSE, which has been the preferred option for at least 3 years, is also on its last legs. Apple has deprecated the OS APIs used by macFUSE since macOS 12.3.</p> | ||
<p>For the past year, we have been desperately searching for an alternative. Our proof of concept using Apple&rsquo;s File Provider framework was not very convincing and would basically require a whole new architecture. Fortunately, you, our community, informed us about an alternative: <a href="https://www.fuse-t.org/">FUSE-T</a>.</p> | ||
<p>FUSE-T is a young project that does not rely on deprecated macOS APIs and can be used as a drop-in-replacement for macFUSE. It requires a much less deep system integration than macFUSE while offering a similar performance. This makes Cryptomator ready for the medium-term future on macOS. But since FUSE-T is quite young, support for it is experimental for now. We encourage you to try it though!</p> | ||
<figure class="text-center"> | ||
<img class="inline-block rounded" src="https://cryptomator.org/img/blog/preferences-fuse-t.png" srcset="https://cryptomator.org/img/blog/preferences-fuse-t.png 1x, https://cryptomator.org/img/blog/[email protected] 2x" alt="Experimental Support for FUSE-T" /> | ||
</figure> | ||
<p>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.</p> | ||
<h2 id="volume-types-overhaul">Volume Types Overhaul</h2> | ||
<p>Looking at the screenshot above, you might have noticed: The volume types have changed, too. That&rsquo;s right, and that&rsquo;s because we rewrote the entire volume type selection and internal wiring logic. It was a huge development effort, but it resulted in a less complex and easier to maintain architecture under the hood. It also resulted in more options for you.</p> | ||
<h3 id="more-options">More Options</h3> | ||
<p>The old implementation basically offered 3 (or 2) options: WebDAV, Dokany, and FUSE. Now, specialized implementations are offered for each OS. For example, on Windows you can select between WinFsp, WinFsp (Local Drive), Dokany, WebDAV (Windows Explorer) and WebDAV (Fallback).</p> | ||
<p>But don&rsquo;t worry, this selection is only important if you have special requirements for the virtual drive. Otherwise, Cryptomator has a new &ldquo;Automatic&rdquo; option and is set up to choose the best suited option for you, and you don&rsquo;t need to worry about it.</p> | ||
<p>We have even added an emergency option: The aforementioned &ldquo;WebDAV (Fallback)&rdquo;. If you can&rsquo;t mount your vault at all, it makes your vault accessible via a local-only server using the web standard WebDAV. We&rsquo;ll have a guide describing this in more detail soon.</p> | ||
<h3 id="winfsp-change-local-vs-network-drive">WinFsp Change: Local vs. Network Drive</h3> | ||
<p>Windows users may notice that their vault is now mounted as a network drive by default. This has the advantage of better performance when listing large directories. The disadvantage is that it cannot be mounted into a directory. Accessing the vault as a privileged user is still possible by using the UNC path.</p> | ||
<figure class="text-center"> | ||
<img class="inline-block rounded" src="https://cryptomator.org/img/blog/winfsp-change.png" srcset="https://cryptomator.org/img/blog/winfsp-change.png 1x, https://cryptomator.org/img/blog/[email protected] 2x" alt="WinFsp Change: Local vs. Network Drive" /> | ||
</figure> | ||
<p>If you really need a local drive, you can always change the volume type in the preferences.</p> | ||
<h3 id="dokany-deprecation">Dokany Deprecation</h3> | ||
<p>With the release of Cryptomator 1.7.0, we will officially deprecate Dokany support.</p> | ||
<p><a href="https://dokan-dev.github.io/">Dokany</a>, like FUSE, provides a file system interface to mount virtual drives without requiring elevated privileges. We started supporting Dokany 3 years ago with version 1.4.0. But things didn&rsquo;t go as smoothly with the Dokany volume as we had hoped, so we decided to focus our development efforts on a single file system interface. All Dokany-related issues on GitHub will be closed, and our general recommendation is to use WinFSP which comes with the EXE installer of Cryptomator. You will still be able to use Dokany, but it won&rsquo;t get any updates and support will eventually be removed.</p> | ||
<p>It was a great time, and we wish the Dokany project all the best!</p> | ||
<h2 id="linux-aarch64-builds">Linux AArch64 Builds</h2> | ||
<p>With Cryptomator 1.7.0, we&rsquo;ll finally ship AArch64 builds of Cryptomator via Flatpak and PPA.</p> | ||
<p>One big obstacle was the aforementioned FUSE file system API on Linux. We were using a rather old project to build the bridge between Cryptomator and FUSE. Thanks to a fantastic development effort started by our lead architect, we now use state-of-the-art technology to implement this bridge. The result is bundled in the library called <a href="https://github.com/cryptomator/jfuse">jFUSE</a>. Not only were we able to change the bridge, we were also able to update to a new major version of FUSE and pave the way to support features like extended attributes.</p> | ||
<p>The AppImage is still x86_x64 only, but we plan to deliver it also in AArch64 architecture eventually.</p> | ||
<h2 id="aes-gcm-new-default-for-content-encryption">AES-GCM: New Default for Content Encryption</h2> | ||
<p>Starting with Cryptomator 1.7.0, newly created vaults will use <a href="https://en.wikipedia.org/wiki/Galois/Counter_Mode">AES-GCM</a> instead of AES-CTR+HMAC for file content encryption.</p> | ||
<p>Nowadays, almost all non-embedded devices offer hardware acceleration of the Galois/Counter Mode of operation, so encryption and decryption should be significantly faster than in the old mode of operation. The support in our underlying cryptographic library <a href="https://github.com/cryptomator/cryptolib">cryptolib</a> was already added in June 2021 with version 2.0.0. But instead of jumping the gun, we gave it a proper testing period and are now confident to ship this improvement to you.</p> | ||
<p>Of course, our mobile apps also support AES-GCM, although vaults created in iOS or Android will continue to use AES-CTR+HMAC for the time being. The mobile apps are scheduled to switch in their next minor release.</p> | ||
<p>You can continue to use your existing vaults as before. There are no vault upgrades and there is no action required on your part. Cryptomator will support both modes of operation.</p> | ||
</description> | ||
<pubDate>Wed, 01 Feb 2023 00:00:00 +0000</pubDate> | ||
<link>https://cryptomator.org/blog/2023/02/01/1-7-0-what-you-need-to-know/</link> | ||
<guid isPermaLink="true">https://cryptomator.org/blog/2023/02/01/1-7-0-what-you-need-to-know/</guid> | ||
|
||
<category>cryptomator</category> | ||
|
||
<category>desktop</category> | ||
|
||
<category>windows</category> | ||
|
||
<category>mac</category> | ||
|
||
<category>linux</category> | ||
|
||
</item> | ||
|
||
</channel> | ||
</rss> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.