Merge branch 'develop'

Author: tobihagemann

docs/desktop/accessing-vaults.md

@@ -37,6 +37,10 @@ Anyone with access to the computer with stored passwords will be able to unlock
 
 <Image src="/img/desktop/unlock-success.png" alt="Vault unlock success dialog" width="512" height="314" />
 
+## Locking a Vault {#locking-a-vault}
+
+To lock a vault, simply click `Lock` and the virtual drive will disappear or render empty. Your files remain encrypted at the vault's location.
+
 ## Manage Files and Folders in Your Vault {#manage-files-and-folders-in-your-vault}
 
 By default, a vault's content will be accessible via an attached virtual drive on your PC.
@@ -55,10 +59,6 @@ Even though your files are shown unencrypted in the virtual drive, they are not
 On Windows, you can choose the drive letter of the virtual drive for each vault using advanced vault options.
 :::
 
-## Locking a Vault {#locking-a-vault}
-
-To lock a vault, simply click `Lock` and the virtual drive will disappear or render empty. Your files remain encrypted at the vault's location.
-
 ## Locate Encrypted File {#locate-encrypted-file}
 
 The Locate Encrypted File feature helps users find the encrypted version of a specific file. This feature is particularly useful when vault files are versioned and the user wants to restore an older version of a file. As Cryptomator encrypts filenames and obfuscates directory structures, users first locate the encrypted file and then restore an older version of the encrypted file with the third party app.
@@ -75,3 +75,19 @@ A file manager window opens showing the encrypted folder and marking the encrypt
   <source src="/vid/locate-encrypted-file.mov" type="video/mp4" />
   Your browser does not support the video tag.
 </video>
+
+## File System Case Sensitivity {#file-system-case-sensitivity}
+
+:::warning
+Cryptomator virtual drives are always case-sensitive. This means `Document.txt` and `document.txt` are treated as two different files, regardless of your operating system.
+:::
+
+This behavior is required for Cryptomator's deterministic [filename encryption](/docs/security/vault.md#filename-encryption) to work correctly across all platforms. While Linux users are accustomed to case-sensitive file systems, this can cause unexpected behavior on Windows and macOS where the default file systems are case-insensitive.
+
+On Windows and macOS, this difference means:
+
+1. Attempting to open `Test.dat` when the file is named `test.dat` will result in a "file not found" error
+2. You can create both `README.md` and `readme.md` in the same directory, which would normally conflict
+3. Some applications may fail when they expect case-insensitive file access
+
+Our recommendation is to avoid creating files with names that differ only in case. Make sure to test applications like backup tools or any other software that will access files in your vault to ensure they handle case-sensitive file systems correctly.

docs/desktop/adding-vaults.md

@@ -79,6 +79,10 @@ This is especially important if you plan to share a vault with someone.
 Additionally, we recommend sharing passwords only over a secure channel, like PGP encypted emails, or end-to-end encrypted chat apps.
 :::
 
+:::info
+Be mindful of your keyboard layout when creating passwords. Special characters and dead keys can behave differently across keyboard layouts (e.g., Dutch vs. English). This may cause password entry issues if you switch keyboard layouts later. For more information, see [Keyboard Layouts and Special Characters](/docs/security/best-practices.md#keyboard-layouts-and-special-characters).
+:::
+
 <Image src="/img/desktop/add-vault-4.png" alt="Choose a strong password for your Cryptomator vault" width="718" height="590" />
 
 :::warning

docs/desktop/password-and-recovery-key.md

@@ -34,6 +34,10 @@ In the opened window, you will be asked for:
 2. A new password. We suggest following our guide on choosing a [strong password](/docs/security/best-practices.md#good-passwords).
 3. Enter the new password again.
 
+:::info
+Be mindful of your keyboard layout when changing passwords. Special characters and dead keys can behave differently across keyboard layouts (e.g., Dutch vs. English). This may cause password entry issues if you switch keyboard layouts later. For more information, see [Keyboard Layouts and Special Characters](/docs/security/best-practices.md#keyboard-layouts-and-special-characters).
+:::
+
 In order to proceed, you must confirm that you understand your action by selecting a checkbox.
 
 Finally, click on the `Change` button to change the password.

docs/security/best-practices.md

@@ -38,6 +38,21 @@ Thus, we recommend using a password manager to generate and store the passwords.
 By doing so, you only have to remember a few or a single secure password.
 Otherwise, we recommend using at least 10 characters, ideally [use sentences instead of words](https://xkcd.com/936/).
 
+### Keyboard Layouts and Special Characters {#keyboard-layouts-and-special-characters}
+
+Be aware that keyboard layout differences can affect password entry. When creating a password, consider these important points:
+
+* Use the same keyboard layout when entering your password. Characters may produce different results depending on your keyboard language setting.
+* Some keyboard layouts use "dead keys" for accented characters. For example, pressing `'` followed by `e` might produce `é` instead of `'e`. This can cause unexpected character conversion in passwords.
+* Characters like `'`, `"`, `` ` ``, `^`, and `~` may behave differently across keyboard layouts and can be particularly problematic.
+
+To avoid issues:
+
+* Test your password immediately after setting it by locking and unlocking your vault.
+* Avoid special characters that may be affected by dead keys if you frequently switch between keyboard layouts.
+* If you must use different keyboard layouts, document which layout was used when creating the password.
+* Consider using alphanumeric characters and basic symbols that remain consistent across keyboard layouts.
+
 ## Backup Strategy {#backup-strategy}
 
 Cryptomator is not a backup solution.

docs/security/security-target.md

@@ -8,26 +8,58 @@ sidebar_position: 1
 
 Cryptomator was designed to solve privacy issues when saving files to cloud storages.
 
+## What Cryptomator Is {#what-cryptomator-is}
+
+Cryptomator is a client-side encryption tool for cloud storage services.
+
 The risk that the cloud provider or third parties access the data stored in the cloud without permission is mitigated.
 Only people who know the vault password are able to read the files in the vault or change the file contents undetected.
 This is true for file contents as well as for filenames.
 
 ## What Cryptomator Encrypts {#what-cryptomator-encrypts}
 
-To allow a working synchronization with the cloud, there are some meta information that Cryptomator does not encrypt.
-These are:
+Cryptomator encrypts:
 
-* access, modification, and creation timestamp of files and folders,
-* number of files and folders in a vault and in the folders, and
-* size of the stored files.
+* file contents,
+* file and folder names, and
+* the directory structure is obfuscated.
+
+For technical details on how these elements are encrypted, see [Vault Cryptography](vault.md).
 
 ## What Cryptomator Is Not {#what-cryptomator-is-not}
 
 In addition, you have to keep in mind what Cryptomator is not.
+
 Protection of the files on the local computer is not the focus of Cryptomator.
-Cryptomator is not a complete replacement for other encryption tools based on container files if the aforementioned meta information should be encrypted.
+Cryptomator cannot provide protection if the local computer is infected with malware which reads entered passwords and file contents (e.g., files in an unlocked vault).
+
 Cryptomator does not provide protection if programs create backup copies of the encrypted files when working with them.
 Such files are not detected by Cryptomator and may remain on the computer even after unlocking a vault.
-Cryptomator cannot provide protection if the local computer is infected with malware which reads entered passwords and file contents (e.g., files in an unlocked vault).
+
+Cryptomator is not a complete replacement for other encryption tools based on container files if metadata (like file sizes and timestamps) should be encrypted.
+
+Cryptomator is not a [steganography tool](https://en.wikipedia.org/wiki/Steganography). It uses recognizable file extensions (`.c9r`, `.c9s`) and stores configuration files (`vault.cryptomator`, `masterkey.cryptomator`) that make it evident that data is encrypted using Cryptomator. The security of your data relies on strong encryption and a secure password, not on hiding the fact that encryption is being used.
 
 To protect against such risks, other methods, like complete disk encryption, immediate installation of system and software updates, and the use of applicable antivirus software, is required.
+
+## What Cryptomator Does Not Encrypt {#what-cryptomator-does-not-encrypt}
+
+To allow a working synchronization with the cloud, there are some metadata that Cryptomator does not encrypt.
+These are:
+
+* access, modification, and creation timestamps of files and folders,
+* number of files and folders in a vault and in the folders, and
+* size of the stored files.
+
+## Accepted Risks {#accepted-risks}
+
+### Filename Swapping Within Same Directory {#filename-swapping-within-same-directory}
+
+An attacker with write access to your cloud storage could swap encrypted filenames within the same directory. While the contents of the files remain secure and any tampering with file contents would be detected, the swapped filenames would not be detected.
+
+This is considered a **low risk** vulnerability because:
+- It requires an attacker to already have write access to your vault
+- File contents remain encrypted and tamper-proof
+- The attack only affects filename-to-content mapping within a single directory
+
+This is an accepted risk because implementing cryptographic binding between filenames and contents would significantly impact performance, especially on mobile devices and remote storage systems. For more information, see the security advisory documented in [GHSA-qwfw-w5qf-7wcj](https://github.com/cryptomator/cryptomator/security/advisories/GHSA-qwfw-w5qf-7wcj).