deploy: fea4648

Author: iammajid

android/index.html

@@ -223,8 +223,8 @@ <h3>Buy a license key</h3>
     <div class="text-center mt-8">
       <p class="text-sm md:text-base leading-relaxed text-gray-700 mb-4">Payments are securely handled by Paddle.</p>
       <p class="text-sm md:text-base leading-relaxed text-gray-700 mb-4">
-<input class="mr-1 rounded text-primary focus:ring-0 focus:ring-offset-0 focus:border-secondary" type="checkbox" id="id-584627391" x-model="acceptTerms" />
-<label for="id-584627391">I accept the <a class="text-primary no-underline hover:underline" href="/terms/">Terms & Conditions</a> as well as the <a class="text-primary no-underline hover:underline" href="/privacy/">Privacy Policy</a>.</label>
+<input class="mr-1 rounded text-primary focus:ring-0 focus:ring-offset-0 focus:border-secondary" type="checkbox" id="id-694783152" x-model="acceptTerms" />
+<label for="id-694783152">I accept the <a class="text-primary no-underline hover:underline" href="/terms/">Terms & Conditions</a> as well as the <a class="text-primary no-underline hover:underline" href="/privacy/">Privacy Policy</a>.</label>
 </p>
       <button :disabled="checkoutData.inProgress || !acceptTerms" @click.prevent="androidLicense.checkout('en')" type="submit" class="btn btn-primary w-full md:w-64 plausible-event-name=android-getkey-checkout">
         <i x-show="!checkoutData.inProgress" class="fas fa-shopping-cart fa-fw" aria-hidden="true"></i><i x-show="checkoutData.inProgress" class="fas fa-spinner fa-spin fa-fw" aria-hidden="true"></i> Checkout

blog/2025/02/05/release-1.15.0/index.html

@@ -204,6 +204,16 @@ <h1>Blog <a href="/feed.xml"><i class="fas fa-rss-square"></i></a></h1>
     </header>
 
 
+      <section class="mb-6">
+        <article class="border rounded shadow bg-white p-4">
+          <p class="text-xs md:text-sm text-gray-600 mb-1">2025-02-05</p>
+          <div class="prose prose-sm md:prose max-w-none md:max-w-none">
+            <h2><a href="/blog/2025/02/05/release-1.15.0/">Cryptomator 1.15.0 is here!</a></h2>
+            <p>We are excited to introduce the latest version of Cryptomator, version 1.15.0! This update not only brings a redesigned user interface but also new features and many improvements.</p>
+          </div>
+        </article>
+      </section>
+    
       <section class="mb-6">
         <article class="border rounded shadow bg-white p-4">
           <p class="text-xs md:text-sm text-gray-600 mb-1">2025-01-24</p>

blog/index.html

@@ -11,9 +11,55 @@
       <title>Cryptomator Blog</title>
       <link>https://cryptomator.org/categories/</link>
     </image>
-    <lastBuildDate>Wed, 05 Feb 2025 15:54:29 +0000</lastBuildDate>
+    <lastBuildDate>Thu, 06 Feb 2025 14:39:55 +0000</lastBuildDate>
     <generator>Hugo</generator>
 
+      <item>
+        <title>Cryptomator 1.15.0 is here!</title>
+        <description>&lt;p&gt;We are excited to introduce the latest version of Cryptomator, version 1.15.0! This update not only brings a redesigned user interface but also new features and many improvements. Let’s take a closer look at the highlights of this release.&lt;/p&gt;
+&lt;h2 id=&#34;whats-new&#34;&gt;What’s New?&lt;/h2&gt;
+&lt;h3 id=&#34;improved-user-interface&#34;&gt;Improved User Interface&lt;/h3&gt;
+&lt;ul&gt;
+&lt;li&gt;&lt;strong&gt;Redesigned Main Window&lt;/strong&gt;: The main window has been revamped to better integrate the app into the system and its design. Additionally, the new layout enhances navigation and groups essential functions so that they are more easily accessible to users.&lt;/li&gt;
+&lt;li&gt;&lt;strong&gt;Compact Vault List&lt;/strong&gt;: The vault list now offers a compact view, which can be enabled in the settings. In this mode, only the vault name is displayed—especially useful for those managing multiple vaults!&lt;/li&gt;
+&lt;/ul&gt;
+&lt;figure class=&#34;text-center&#34;&gt;
+  &lt;img class=&#34;inline-block rounded&#34; src=&#34;https://cryptomator.org/img/blog/create-vault.png&#34; srcset=&#34;https://cryptomator.org/img/blog/create-vault.png 1x, https://cryptomator.org/img/blog/[email protected] 2x&#34; alt=&#34;Screenshot of creating a vault in the Cryptomator app&#34; /&gt;
+&lt;/figure&gt;
+&lt;figure class=&#34;text-center&#34;&gt;
+  &lt;img class=&#34;inline-block rounded&#34; src=&#34;https://cryptomator.org/img/blog/compact-vault-list.png&#34; srcset=&#34;https://cryptomator.org/img/blog/compact-vault-list.png 1x, https://cryptomator.org/img/blog/[email protected] 2x&#34; alt=&#34;Screenshot showing the new Compact List View&#34; /&gt;
+&lt;/figure&gt;
+&lt;h3 id=&#34;enhanced-compatibility--new-features&#34;&gt;Enhanced Compatibility &amp;amp; New Features&lt;/h3&gt;
+&lt;ul&gt;
+&lt;li&gt;&lt;strong&gt;New Language&lt;/strong&gt;: Cryptomator is now available in Uyghur! A huge thank you to our community for this contribution. If you’d like to help with translations, visit us &lt;a href=&#34;https://translate.cryptomator.org&#34;&gt;here&lt;/a&gt;.&lt;/li&gt;
+&lt;li&gt;&lt;strong&gt;Zero Dependency AppImage&lt;/strong&gt;: The AppImage no longer requires libfuse (version 2) to start. This makes the AppImage fully self-contained and compatible with almost all Linux systems.&lt;/li&gt;
+&lt;li&gt;&lt;strong&gt;Certificate Store&lt;/strong&gt;: Cryptomator now uses the system’s certificate stores (macOS, Windows) or a custom PKCS12 file (Linux) for HTTPS connections. This change ensures better compatibility with enterprise environments where custom certificates are used.&lt;/li&gt;
+&lt;li&gt;&lt;strong&gt;Improved Error Handling When Unlocking&lt;/strong&gt;: If a vault is read-only, this is now indicated to the user, and a retry in read-only mode is possible. This ensures greater transparency, prevents unexpected issues, and allows access to files even in restricted environments.&lt;/li&gt;
+&lt;/ul&gt;
+&lt;h2 id=&#34;bugfixes&#34;&gt;Bugfixes&lt;/h2&gt;
+&lt;ul&gt;
+&lt;li&gt;A bug in the &lt;strong&gt;cryptographic file system&lt;/strong&gt; has been fixed. In very rare cases, the cryptographic content of a file became corrupted when writing and truncating simultaneously. The bug was discovered through our automated tests and was quickly resolved.&lt;/li&gt;
+&lt;li&gt;&lt;strong&gt;Supporter Certificate Management&lt;/strong&gt;: It is now possible to manage the supporter certificate. Once entered, it is hidden if valid and can only be removed. This prevents easy marking and copying, enhancing certificate security.&lt;/li&gt;
+&lt;li&gt;Vaults can be added to &lt;strong&gt;Dolphin’s Quick Access&lt;/strong&gt; again. This makes navigation and access to encrypted files easier for KDE users.&lt;/li&gt;
+&lt;/ul&gt;
+&lt;h2 id=&#34;other-changes&#34;&gt;Other Changes&lt;/h2&gt;
+&lt;ul&gt;
+&lt;li&gt;&lt;strong&gt;Updated to JDK 23&lt;/strong&gt; and &lt;strong&gt;JavaFX 23.0.1&lt;/strong&gt; for better performance and stability, ensuring compatibility with modern development standards.&lt;/li&gt;
+&lt;li&gt;&lt;strong&gt;Updated translations&lt;/strong&gt; for many supported languages, ensuring a better user experience across different regions.&lt;/li&gt;
+&lt;/ul&gt;
+&lt;h2 id=&#34;update-now&#34;&gt;Update Now!&lt;/h2&gt;
+&lt;p&gt;Cryptomator 1.15.0 is now available! Download the latest version directly from our download page and enjoy the new features and improvements.&lt;/p&gt;
+&lt;p&gt;As always, we appreciate your feedback and support! If you have any questions or encounter any issues, feel free to visit our &lt;a href=&#34;https://community.cryptomator.org/&#34;&gt;community forum&lt;/a&gt; or check out our &lt;a href=&#34;https://github.com/cryptomator/cryptomator/releases/tag/1.15.0&#34;&gt;GitHub repository&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;Enjoy the new version! 🎉&lt;/p&gt;
+</description>
+        <pubDate>Wed, 05 Feb 2025 00:00:00 +0000</pubDate>
+        <link>https://cryptomator.org/blog/2025/02/05/release-1.15.0/</link>
+        <guid isPermaLink="true">https://cryptomator.org/blog/2025/02/05/release-1.15.0/</guid>
+        
+        <category>cryptomator</category>
+        
+      </item>
+    
       <item>
         <title>Cryptomator for Android Now on Accrescent</title>
         <description>&lt;h2 id=&#34;cryptomator-for-android-now-on-accrescent&#34;&gt;Cryptomator for Android Now on Accrescent&lt;/h2&gt;
@@ -351,60 +397,5 @@ Also see &lt;strong&gt;Q7.&lt;/strong&gt;&lt;/p&gt;
 
       </item>
 
-      <item>
-        <title>Cryptomator Hub 1.3.0: The Account Key Update</title>
-        <description>&lt;p&gt;The release of Cryptomator Hub 1.3.0 marks an exciting feature update, which introduces an &lt;em&gt;Account Key&lt;/em&gt; for users. This update, while necessary and beneficial, will require active participation from users. Here&amp;rsquo;s what to expect during the transition from version 1.2.x to 1.3.0.&lt;/p&gt;
-&lt;h2 id=&#34;information_source-preparation-is-key&#34;&gt;&amp;#x2139;&amp;#xfe0f; Preparation is Key&lt;/h2&gt;
-&lt;p&gt;Before we dive into the upgrade process, ensure every vault admin secures a backup of their &lt;em&gt;Vault Recovery Keys&lt;/em&gt; and &lt;em&gt;Vault Admin Passwords&lt;/em&gt;. &lt;strong&gt;&amp;#x26a0;&amp;#xfe0f; Doubling down on this step is critical; your backups are your safety net. Without them, our hands are tied.&lt;/strong&gt;&lt;/p&gt;
-&lt;h2 id=&#34;arrow_up-updating-cryptomator-hub-server-to-130&#34;&gt;&amp;#x2b06;&amp;#xfe0f; Updating Cryptomator Hub (Server) to 1.3.0&lt;/h2&gt;
-&lt;p&gt;This section is only relevant for administrators who host their own Cryptomator Hub instance. If you&amp;rsquo;re using our managed service, you can skip this section. We will reach out to you to arrange a date and time to update your instance.&lt;/p&gt;
-&lt;p&gt;As mentioned above, if you&amp;rsquo;re an administrator of a self-hosted Cryptomator Hub instance, follow these steps to update Cryptomator Hub:&lt;/p&gt;
-&lt;ol&gt;
-&lt;li&gt;&lt;a href=&#34;https://docs.cryptomator.org/en/latest/hub/setup/#backup&#34;&gt;Back up the database&lt;/a&gt;. &lt;strong&gt;&amp;#x26a0;&amp;#xfe0f; The importance of a working backup cannot be overstated.&lt;/strong&gt;&lt;/li&gt;
-&lt;li&gt;Refresh your container image to the latest version: &lt;code&gt;ghcr.io/cryptomator/hub:1.3.0&lt;/code&gt;
-&lt;ul&gt;
-&lt;li&gt;Skip this step if you&amp;rsquo;re using the &lt;code&gt;stable&lt;/code&gt; tag. We will update the &lt;code&gt;stable&lt;/code&gt; tag to point to the new version in a couple of weeks.&lt;/li&gt;
-&lt;/ul&gt;
-&lt;/li&gt;
-&lt;li&gt;Implement the changes within your container orchestrator. Monitor for healthy pod statuses before proceeding.&lt;/li&gt;
-&lt;/ol&gt;
-&lt;h2 id=&#34;arrow_up-updating-cryptomator-desktop-client-to-1110&#34;&gt;&amp;#x2b06;&amp;#xfe0f; Updating Cryptomator (Desktop Client) to 1.11.0&lt;/h2&gt;
-&lt;p&gt;Updating the Cryptomator desktop application is recommended for all users, but not technically required for now. Vaults can still be unlocked using an old version. This backward compatibility provides flexibility for a gradual rollout of the updated app. Nevertheless, making changes to access, incl. adding new members to a vault and adding new devices, requires Cryptomator 1.11.0 or higher.&lt;/p&gt;
-&lt;h2 id=&#34;key-introducing-account-keys&#34;&gt;&amp;#x1f511; Introducing Account Keys&lt;/h2&gt;
-&lt;p&gt;With the updated app, users will encounter a two-step migration on their first unlock attempt:&lt;/p&gt;
-&lt;ol&gt;
-&lt;li&gt;Secure and store their new personal &lt;em&gt;Account Key&lt;/em&gt;. &lt;strong&gt;&amp;#x26a0;&amp;#xfe0f; It&amp;rsquo;s crucial for future logins from other devices.&lt;/strong&gt;&lt;/li&gt;
-&lt;li&gt;Use the &lt;em&gt;Account Key&lt;/em&gt; to link their Cryptomator device to their account.&lt;/li&gt;
-&lt;/ol&gt;
-&lt;p&gt;This procedure is a one-time requirement for every user. It allows users to self-manage linked devices and vault owners to more easily manage access without having to frequently regrant permissions each time a user logs in from a new device.&lt;/p&gt;
-&lt;h2 id=&#34;bust_in_silhouette-claiming-vault-ownership-and-granting-access&#34;&gt;&amp;#x1f464; Claiming Vault Ownership and Granting Access&lt;/h2&gt;
-&lt;p&gt;After updating to Hub 1.3.0, vault owners (formerly known as vault admins) are prompted to claim their vault again using the &lt;em&gt;Vault Admin Password&lt;/em&gt;. Initially, only one user can claim ownership. Subsequently, this primary owner can grant ownership rights to others, thus eliminating the need to share the &lt;em&gt;Vault Admin Password&lt;/em&gt;.&lt;/p&gt;
-&lt;p&gt;Once vault members have navigated through the account migration, vault owners should refresh vault permissions. This action will securely distribute the necessary vault keys to the users.&lt;/p&gt;
-&lt;h2 id=&#34;question-frequently-asked-questions&#34;&gt;&amp;#x2753; Frequently Asked Questions&lt;/h2&gt;
-&lt;p&gt;&lt;strong&gt;Q: What exactly is my &lt;em&gt;Account Key&lt;/em&gt;?&lt;/strong&gt;&lt;br&gt;
-&lt;strong&gt;A:&lt;/strong&gt; The &lt;em&gt;Account Key&lt;/em&gt; is your personal secret, required for registering new devices and establishing your identity across different Cryptomator apps and browsers. Treat it with the same level of security as you would with any important password.&lt;/p&gt;
-&lt;p&gt;&lt;strong&gt;Q: How do I retrieve my &lt;em&gt;Account Key&lt;/em&gt; if I lose it?&lt;/strong&gt;&lt;br&gt;
-&lt;strong&gt;A:&lt;/strong&gt; You can retrieve your &lt;em&gt;Account Key&lt;/em&gt; by logging into your Cryptomator Hub account and navigating to the &lt;em&gt;Profile&lt;/em&gt; page. There, you can view your &lt;em&gt;Account Key&lt;/em&gt;. If your browser doesn&amp;rsquo;t have access and you can&amp;rsquo;t retrieve it anymore, you can reset your account. In this case, you will lose access to all your vaults and the vault owner(s) will have to grant you access again.&lt;/p&gt;
-&lt;p&gt;&lt;strong&gt;Q: Will the update affect my existing vaults and the data they contain?&lt;/strong&gt;&lt;br&gt;
-&lt;strong&gt;A:&lt;/strong&gt; No, the update will not affect your vaults or the data they contain. This update only affects the unlock process and access management, not the encrypted data itself.&lt;/p&gt;
-&lt;p&gt;&lt;strong&gt;Q: What happens to the &lt;em&gt;Vault Admin Password&lt;/em&gt; after I reclaim ownership?&lt;/strong&gt;&lt;br&gt;
-&lt;strong&gt;A:&lt;/strong&gt; Upon reclaim, the &lt;em&gt;Vault Admin Password&lt;/em&gt; becomes obsolete. You may destroy any copies of it. Compromised &lt;em&gt;Vault Admin Passwords&lt;/em&gt; don&amp;rsquo;t pose a threat to the security of the vault.&lt;/p&gt;
-&lt;p&gt;&lt;strong&gt;Q: Is the process for adding new users to a vault different?&lt;/strong&gt;&lt;br&gt;
-&lt;strong&gt;A:&lt;/strong&gt; The difference is that you don&amp;rsquo;t grant access to each and every device, but to the user once, thanks to the &lt;em&gt;Account Key&lt;/em&gt;. The user can link their devices to their account and access the vault from any of them without having to ask for permission again.&lt;/p&gt;
-&lt;p&gt;&lt;strong&gt;Q: What should I do if I encounter problems during the upgrade process?&lt;/strong&gt;&lt;br&gt;
-&lt;strong&gt;A:&lt;/strong&gt; If you encounter any problems during the upgrade process, please contact us at &lt;a href=&#34;mailto:[email protected]&#34;&gt;[email protected]&lt;/a&gt;.&lt;/p&gt;
-&lt;h2 id=&#34;clipboard-wrapping-up&#34;&gt;&amp;#x1f4cb; Wrapping Up&lt;/h2&gt;
-&lt;p&gt;The upgrade to Cryptomator Hub 1.3.0 and Cryptomator 1.11.0 is more than a routine update. It&amp;rsquo;s a shift towards greater security and user agency. Prepare for the update by backing up essential data, and follow the outlined steps to ensure a smooth transition. Embrace the change, as it brings forward a more robust and user-friendly way to manage your vaults.&lt;/p&gt;
-</description>
-        <pubDate>Fri, 01 Dec 2023 00:00:00 +0000</pubDate>
-        <link>https://cryptomator.org/blog/2023/12/01/hub-1.3.0/</link>
-        <guid isPermaLink="true">https://cryptomator.org/blog/2023/12/01/hub-1.3.0/</guid>
-        
-        <category>cryptomator</category>
-        
-        <category>hub</category>
-        
-      </item>
-    
   </channel>
 </rss>

categories/feed.xml

@@ -223,8 +223,8 @@ <h3>Lizenzschlüssel kaufen</h3>
     <div class="text-center mt-8">
       <p class="text-sm md:text-base leading-relaxed text-gray-700 mb-4">Zahlungen werden über Paddle abgewickelt.</p>
       <p class="text-sm md:text-base leading-relaxed text-gray-700 mb-4">
-<input class="mr-1 rounded text-primary focus:ring-0 focus:ring-offset-0 focus:border-secondary" type="checkbox" id="id-149825637" x-model="acceptTerms" />
-<label for="id-149825637">Ich akzeptiere die <a class="text-primary no-underline hover:underline" href="/de/terms/">AGB</a> sowie die <a class="text-primary no-underline hover:underline" href="/de/privacy/">Datenschutzerklärung</a>.</label>
+<input class="mr-1 rounded text-primary focus:ring-0 focus:ring-offset-0 focus:border-secondary" type="checkbox" id="id-985473621" x-model="acceptTerms" />
+<label for="id-985473621">Ich akzeptiere die <a class="text-primary no-underline hover:underline" href="/de/terms/">AGB</a> sowie die <a class="text-primary no-underline hover:underline" href="/de/privacy/">Datenschutzerklärung</a>.</label>
 </p>
       <button :disabled="checkoutData.inProgress || !acceptTerms" @click.prevent="androidLicense.checkout('de')" type="submit" class="btn btn-primary w-full md:w-64 plausible-event-name=android-getkey-checkout">
         <i x-show="!checkoutData.inProgress" class="fas fa-shopping-cart fa-fw" aria-hidden="true"></i><i x-show="checkoutData.inProgress" class="fas fa-spinner fa-spin fa-fw" aria-hidden="true"></i> Zur Zahlung