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
Remove outdated recovery setup options from E2EE docs (#30681)
* Deprecate secure_backup_required and secure_backup_setup_methods in docs.
* Wording enhancements.
Co-authored-by: Richard van der Hoff <[email protected]>
* Use removal, not deprecation for sake of clarity.
Co-authored-by: Richard van der Hoff <[email protected]>
* Use removal, not deprecation for sake of clarity.
Co-authored-by: Richard van der Hoff <[email protected]>
* prettier
---------
Co-authored-by: Richard van der Hoff <[email protected]>
Co-authored-by: Richard van der Hoff <[email protected]>
Copy file name to clipboardExpand all lines: docs/e2ee.md
+9-34Lines changed: 9 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,45 +38,20 @@ When `force_disable` is true:
38
38
Note: If the server is configured to forcibly enable encryption for some or all rooms,
39
39
this behaviour will be overridden.
40
40
41
-
# Secure backup
41
+
# Setting up recovery
42
42
43
43
By default, Element strongly encourages (but does not require) users to set up
44
-
Secure Backup so that cross-signing identity key and message keys can be
45
-
recovered in case of a disaster where you lose access to all active devices.
44
+
recovery so that you can access history on your new devices as well as retain access to your message history and cryptographic identity when you lose all of your devices.
46
45
47
-
## Requiring secure backup
46
+
## Removal of old settings
48
47
49
-
To require Secure Backup to be configured before Element can be used, set the
50
-
following on your homeserver's `/.well-known/matrix/client` config:
48
+
Support for the configuration options `secure_backup_required` and `secure_backup_setup_methods`
49
+
in the `/.well-known/matrix/client` config has been removed.
51
50
52
-
```json
53
-
{
54
-
"io.element.e2ee": {
55
-
"secure_backup_required": true
56
-
}
57
-
}
58
-
```
59
-
60
-
## Preferring setup methods
61
-
62
-
By default, Element offers users a choice of a random key or user-chosen
63
-
passphrase when setting up Secure Backup. If a homeserver admin would like to
64
-
only offer one of these, you can signal this via the
65
-
`/.well-known/matrix/client` config, for example:
66
-
67
-
```json
68
-
{
69
-
"io.element.e2ee": {
70
-
"secure_backup_setup_methods": ["passphrase"]
71
-
}
72
-
}
73
-
```
74
-
75
-
The field `secure_backup_setup_methods` is an array listing the methods the
76
-
client should display. Supported values currently include `key` and
77
-
`passphrase`. If the `secure_backup_setup_methods` field is not present or
78
-
exists but does not contain any supported methods, Element will fallback to the
79
-
default value of: `["key", "passphrase"]`.
51
+
Setting up recovery is now always recommended to all users by showing a one-off toast and a
52
+
permanent red dot on the _Encryption_ tab in the _Settings_ dialog. When creating a new
53
+
recovery key, the UI only supports auto-generated keys. Using an existing (custom) passphrase
54
+
still works, but is not exposed in the UI when setting up recovery.
0 commit comments