Skip to content

Commit a3b8c67

Browse files
authored
Merge pull request element-hq#15003 from vector-im/jryans/secure-backup-required
Document .well-known E2EE secure backup setting
2 parents a329dd6 + 3800fe0 commit a3b8c67

File tree

1 file changed

+27
-1
lines changed

1 file changed

+27
-1
lines changed

docs/e2ee.md

Lines changed: 27 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,36 @@ For private room creation, Element will default to encryption on but give you th
77

88
Set the following on your homeserver's
99
`/.well-known/matrix/client` config:
10+
1011
```json
1112
{
12-
"im.vector.riot.e2ee": {
13+
"io.element.e2ee": {
1314
"default": false
1415
}
1516
}
1617
```
18+
19+
# Secure backup
20+
21+
By default, Element strongly encourages (but does not require) users to set up
22+
Secure Backup so that cross-signing identity key and message keys can be
23+
recovered in case of a disaster where you lose access to all active devices.
24+
25+
## Requiring secure backup
26+
27+
To require Secure Backup to be configured before Element can be used, set the
28+
following on your homeserver's `/.well-known/matrix/client` config:
29+
30+
```json
31+
{
32+
"io.element.e2ee": {
33+
"secure_backup_required": true
34+
}
35+
}
36+
```
37+
38+
# Compatibility
39+
40+
The settings above were first proposed under a `im.vector.riot.e2ee` key, which
41+
is now deprecated. Element will check for either key, preferring
42+
`io.element.e2ee` if both exist.

0 commit comments

Comments
 (0)