bekucera/element-web
1
0
Fork 0
mirror of https://github.com/element-hq/element-web.git synced 2025-09-17 11:04:05 +02:00
Code Issues Packages Projects Releases Wiki Activity

Remove outdated recovery setup options from E2EE docs (#30681)

Browse Source 
* Deprecate secure_backup_required and secure_backup_setup_methods in docs.

* Wording enhancements.

Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>

* Use removal, not deprecation for sake of clarity.

Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>

* Use removal, not deprecation for sake of clarity.

Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>

* prettier

---------

Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
Co-authored-by: Richard van der Hoff <richard@matrix.org>
This commit is contained in:
mxandreas
2025-09-08 21:16:03 +03:00
committed by GitHub
parent d70a3a695e
commit 207173db95
1 changed files with 9 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

43
docs/e2ee.md
View File

@@ -38,45 +38,20 @@ When `force_disable` is true:
Note: If the server is configured to forcibly enable encryption for some or all rooms, Note: If the server is configured to forcibly enable encryption for some or all rooms,
this behaviour will be overridden. this behaviour will be overridden.
# Secure backup # Setting up recovery
By default, Element strongly encourages (but does not require) users to set up By default, Element strongly encourages (but does not require) users to set up
Secure Backup so that cross-signing identity key and message keys can be 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.
recovered in case of a disaster where you lose access to all active devices.
## Requiring secure backup ## Removal of old settings
To require Secure Backup to be configured before Element can be used, set the Support for the configuration options `secure_backup_required` and `secure_backup_setup_methods`
following on your homeserver's `/.well-known/matrix/client` config: in the `/.well-known/matrix/client` config has been removed.
```json Setting up recovery is now always recommended to all users by showing a one-off toast and a
{ permanent red dot on the _Encryption_ tab in the _Settings_ dialog. When creating a new
"io.element.e2ee": { recovery key, the UI only supports auto-generated keys. Using an existing (custom) passphrase
"secure_backup_required": true still works, but is not exposed in the UI when setting up recovery.
}
}
```
## Preferring setup methods
By default, Element offers users a choice of a random key or user-chosen
passphrase when setting up Secure Backup. If a homeserver admin would like to
only offer one of these, you can signal this via the
`/.well-known/matrix/client` config, for example:
```json
{
"io.element.e2ee": {
"secure_backup_setup_methods": ["passphrase"]
}
}
```
The field `secure_backup_setup_methods` is an array listing the methods the
client should display. Supported values currently include `key` and
`passphrase`. If the `secure_backup_setup_methods` field is not present or
exists but does not contain any supported methods, Element will fallback to the
default value of: `["key", "passphrase"]`.
# Compatibility # Compatibility