You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/android/settings.rst
+2-2
Original file line number
Diff line number
Diff line change
@@ -80,7 +80,7 @@ The Android documentation contains `some more details <https://developer.android
80
80
Starting from version 1.3.0, this protection can be disabled in the settings. We rather recommend to use the app without a blue light filter because this is more secure.
81
81
82
82
If you want to disable protection, the blue light filter or any app obscuring Cryptomator has to be disabled one time.
83
-
Afterwards, the settings can be opened and the option "Disable app when obscured" can be disabled. And then the relevant apps can be reenabled again.
83
+
Afterwards, the settings can be opened and the option "Disable app when obscured" can be disabled. And then the relevant apps can be re-enabled again.
84
84
85
85
To identify apps which could cause this, open the Android settings and navigate to **Settings - Apps - Advanced (gear icon) - Draw over other apps**.
86
86
This will list the installed Apps and will show you which ones are allowed to draw over other apps.
@@ -204,7 +204,7 @@ Which pictures will be tracked, depends on the Android version on your phone:
204
204
Cache
205
205
----------------------
206
206
207
-
Introduced in version 1.5.0, if enbaled, all downloaded files will be cached (encrypted) on the file system. Further downloads will only verify with the server, that the cached file is still the latest version.
207
+
Introduced in version 1.5.0, if enabled, all downloaded files will be cached (encrypted) on the file system. Further downloads will only verify with the server, that the cached file is still the latest version.
208
208
If so it will not be downloaded again but directly retrieved from the file system. The cache is implemented using a least recently used mechanism, that means, the oldest entry will be overwritten if the max cache size is reached.
Copy file name to clipboardExpand all lines: source/android/vault-management.rst
+3-3
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ Choose between *Dropbox*, *Google Drive*, *OneDrive* (works also with *OneDrive
34
34
:alt:How to create a new vault with Android
35
35
:width:346px
36
36
37
-
If not already done, you have to create the connection between the Cryptomator app and your storage provider account. Please follow the instructions in the :ref:`Cloud Management <android/cloud-management>` chapter and contiune later here.
37
+
If not already done, you have to create the connection between the Cryptomator app and your storage provider account. Please follow the instructions in the :ref:`Cloud Management <android/cloud-management>` chapter and continue later here.
38
38
39
39
Now that you've established a connection, you'll add the existing vault.
40
40
@@ -101,7 +101,7 @@ Choose between *Dropbox*, *Google Drive*, *OneDrive* (works also with *OneDrive
101
101
:alt:How add a vault with Android
102
102
:width:346px
103
103
104
-
If not already done, you have to create the connection between the Cryptomator app and your storage provider account. Please follow the instructions in the :ref:`Cloud Management <android/cloud-management>` chapter and contiune later here.
104
+
If not already done, you have to create the connection between the Cryptomator app and your storage provider account. Please follow the instructions in the :ref:`Cloud Management <android/cloud-management>` chapter and continue later here.
105
105
106
106
Now that you've established a connection, you'll add the existing vault.
107
107
@@ -217,7 +217,7 @@ If you want to change the name of a specific vault in Cryptomator, you select th
217
217
218
218
Choose a new name and confirm using the ``RENAME`` button.
Copy file name to clipboardExpand all lines: source/desktop/setup.rst
+1-1
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ Install Cryptomator on Linux
46
46
47
47
Cryptomator is available on Linux via ``Flatpak``, ``PPA`` and ``AUR`` package managers, and as an AppImage (an ``.appimage`` file).
48
48
49
-
The easiest and recommended way of installing Cryptomator on Linux is by downloading Cryptomator's AppImage (an ``.appimage`` file) - as it works on almost all distrubtions.
49
+
The easiest and recommended way of installing Cryptomator on Linux is by downloading Cryptomator's AppImage (an ``.appimage`` file) - as it works on almost all distributions.
50
50
Just remember to `make it executable <https://docs.appimage.org/user-guide/run-appimages.html#running-appimages>`_ before you try to run it.
51
51
52
52
Visit our `downloads page <https://cryptomator.org/downloads>`_ to choose your preferred installation method.
Copy file name to clipboardExpand all lines: source/desktop/volume-type.rst
+2-2
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ What is a FUSE volume type?
33
33
---------------------------
34
34
35
35
Filesystem in Userspace (`FUSE <https://en.wikipedia.org/wiki/Filesystem_in_Userspace>`_) is a filesystem interface originally developed for Unix operating systems that let non-privileged users create their own file systems without editing kernel code.
36
-
Which means, FUSE does not require admin privileges and is has good support across all major desktop operating systems.
36
+
Which means, FUSE does not require admin privileges and has good support across all major desktop operating systems.
37
37
FUSE volume type also delivers good performance when working on files.
38
38
39
39
All FUSE related volume types support custom mount options, but every option must be prefixed with ``-o``.
@@ -199,5 +199,5 @@ WebDAV (HTTP Address)
199
199
This volume type is always present and comes in handy when all other volume types fail to mount.
200
200
It starts a local-only WebDAV server, which can be manually integrated into the system or accessed using a third-party application, like `Cyberduck <https://cyberduck.io/>`_.
201
201
Check out the regarding manuals for your OS on how to connect to a WebDAV server.
202
-
The address of Cryptomators local-only WebDAV server can be copied from the vault detail screen by clicking the green "Copy" button.
202
+
The address of Cryptomator's local-only WebDAV server can be copied from the vault detail screen by clicking the green "Copy" button.
Copy file name to clipboardExpand all lines: source/hub/access-vault.rst
+1-1
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,7 @@ When you finished the account setup in Hub, unlock the vault again.
70
70
4. Register Device
71
71
^^^^^^^^^^^^^^^^^^
72
72
73
-
If you just did setup your accout, a vault owner needs to grant you access for the requested vault as described :ref:`here <hub/vault-management/updating-permission>`. Retry unlocking the vault after the vault owner granted you access.
73
+
If you just did setup your account, a vault owner needs to grant you access for the requested vault as described :ref:`here <hub/vault-management/updating-permission>`. Retry unlocking the vault after the vault owner granted you access.
74
74
75
75
.. image:: ../img/hub/unlock-access-denied.png
76
76
:alt:Access is denied since it has not been granted by a vault owner yet
Copy file name to clipboardExpand all lines: source/hub/admin.rst
+5-5
Original file line number
Diff line number
Diff line change
@@ -68,22 +68,22 @@ The following events are logged:
68
68
Device
69
69
"""""""
70
70
71
-
- **Register Device** - A user :ref:`registered a new device <hub/access-vault/unlocking-a-vault/add-device>`. This can be e.g. a Cryptomator app (desktop/mobile) to unlock a vault or a web browser to access Cryptomator Hub.
71
+
- **Register Device** - A user :ref:`registered a new device <hub/access-vault/unlocking-a-vault/add-device>`. This can be, e.g., a Cryptomator app (desktop/mobile) to unlock a vault or a web browser to access Cryptomator Hub.
72
72
- **Remove Device** – A user :ref:`removed a device <hub/your-account/profile/authorized-devices>`.
73
73
74
74
Web of Trust
75
75
""""""""""""
76
76
77
77
- **Signed Identity** – A user :ref:`signed the identity of another user <hub/vault-management/wot>`.
78
-
- **Update Wot Setting** – A user updated :ref:`Web-of-Trust settings<hub/vault-management/wot>`, e.g. the ``wot_max_depth``.
78
+
- **Update Wot Setting** – A user updated :ref:`Web-of-Trust settings<hub/vault-management/wot>`, e.g., the ``wot_max_depth``.
79
79
80
80
Vault
81
81
""""""
82
82
83
83
- **Add Vault Member** – A vault owner :ref:`added a member to a vault <hub/vault-management/add-user>`. This only adds the member but does not derive the vault key for the new member.
84
84
- **Create Vault** – A user :ref:`created a vault <hub/vault-management/create-vault>`.
85
85
- **Grant Vault Access** – A user :ref:`derived the vault key for the new member <hub/vault-management/updating-permission>`.
86
-
- **Retrieve Vault Key** – A user retrieved a vault key. This happens when a user :ref:`unlocks a vault <hub/access-vault/unlocking-a-vault>` but also e.g. when a owner manages the vault. The IP address and device information are optional for legacy reasons.
86
+
- **Retrieve Vault Key** – A user retrieved a vault key. This happens when a user :ref:`unlocks a vault <hub/access-vault/unlocking-a-vault>` but also, e.g., when an owner manages the vault. The IP address and device information are optional for legacy reasons.
87
87
- **Remove Vault Member** – A vault owner removed a member from a vault.
88
88
- **Update Vault Member** – A vault owner :ref:`changed a member’s role <hub/vault-management/change-ownership>` (owner or user).
89
89
- **Update Vault** – A vault owner :ref:`updated the vault metadata <hub/vault-management/edit-vault-metadata>`. This includes the vault name or description.
@@ -92,8 +92,8 @@ Account
92
92
""""""""
93
93
94
94
- **Account Key Changed** – A user :ref:`re-generated the account key <hub/your-account/profile/regenerate-account-key>`. This also logs ``User Keys Change`` because changing the account key also changes parts of the user keys.
95
-
- **Reset User Account** – A user :ref:`resetted it's account <hub/your-account/reset-account>`.
96
-
- **User Keys Change** – A user changed it's keys. This happens when e.g. the user :ref:`finished the account setup <hub/your-account/setup>` or when the ``Account Key Changed``.
95
+
- **Reset User Account** – A user :ref:`reset their account <hub/your-account/reset-account>`.
96
+
- **User Keys Change** – A user changed their keys. This happens when, e.g., the user :ref:`finished the account setup <hub/your-account/setup>` or when the ``Account Key Changed``.
Copy file name to clipboardExpand all lines: source/hub/vault-management.rst
+1-1
Original file line number
Diff line number
Diff line change
@@ -177,7 +177,7 @@ Cryptomator Hub uses a Web of Trust (WoT) to verify the identity of users during
177
177
178
178
The WoT state of a user is displayed in the vault details page. The state can be one of the following:
179
179
180
-
* **Unverified**: There is no turst chain between you and the specific user. Indicated with a red shield. You can change this by verifying the user.
180
+
* **Unverified**: There is no trust chain between you and the specific user. Indicated with a red shield. You can change this by verifying the user.
181
181
* **Verified**: There is a trust chain between you and the specific user. Indicated with a green shield. You or a user you trust has verified the user.
182
182
183
183
To verify ``alice``, click on the red shield icon and select ``Check Idenditiy...``
0 commit comments