From 867c96c22bfe708193582e323d48903a258f12cb Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Fri, 10 Apr 2026 16:16:16 +0100 Subject: [PATCH 01/11] Specify m.key_backup account data (MSC4287) Signed-off-by: Andy Balaam --- .../client_server/newsfragments/2354.feature | 1 + content/client-server-api/_index.md | 2 + .../modules/key_backup_enabled.md | 44 +++++++++++++++++++ .../client-server/definitions/key_backup.yaml | 22 ++++++++++ data/event-schemas/examples/m.key_backup.yaml | 7 +++ data/event-schemas/schema/m.key_backup.yaml | 26 +++++++++++ 6 files changed, 102 insertions(+) create mode 100644 changelogs/client_server/newsfragments/2354.feature create mode 100644 content/client-server-api/modules/key_backup_enabled.md create mode 100644 data/api/client-server/definitions/key_backup.yaml create mode 100644 data/event-schemas/examples/m.key_backup.yaml create mode 100644 data/event-schemas/schema/m.key_backup.yaml diff --git a/changelogs/client_server/newsfragments/2354.feature b/changelogs/client_server/newsfragments/2354.feature new file mode 100644 index 00000000..13a56a7e --- /dev/null +++ b/changelogs/client_server/newsfragments/2354.feature @@ -0,0 +1 @@ +Specify m.key_backup account data (MSC4287). diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md index d790c924..5d655509 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -4280,6 +4280,7 @@ that profile. | [Policy Servers](#policy-servers) | Optional | Optional | Optional | Optional | Optional | | [OpenID](#openid) | Optional | Optional | Optional | Optional | Optional | | [Recently used emoji](#recently-used-emoji) | Optional | Optional | Optional | Optional | Optional | +| [Key Backup Enabled](#key-backup-enabled) | Optional | Optional | Optional | Optional | Optional | | [Reference Relations](#reference-relations) | Optional | Optional | Optional | Optional | Optional | | [Reporting Content](#reporting-content) | Optional | Optional | Optional | Optional | Optional | | [Rich replies](#rich-replies) | Optional | Optional | Optional | Optional | Optional | @@ -4385,5 +4386,6 @@ systems. {{% cs-module name="Event replacements" filename="event_replacements" %}} {{% cs-module name="Event annotations and reactions" filename="event_annotations" %}} {{% cs-module name="Recently used emoji" filename="recent_emoji" %}} +{{% cs-module name="Key backup enabled" filename="key_backup_enabled" %}} {{% cs-module name="Threading" filename="threading" %}} {{% cs-module name="Reference relations" filename="reference_relations" %}} diff --git a/content/client-server-api/modules/key_backup_enabled.md b/content/client-server-api/modules/key_backup_enabled.md new file mode 100644 index 00000000..f0e188b3 --- /dev/null +++ b/content/client-server-api/modules/key_backup_enabled.md @@ -0,0 +1,44 @@ +### Key backup enabled + +{{% added-in v="1.19" %}} + +This module enables clients to track a user's preference about enabling or +disabling [server-side backups of room keys](#server-side-key-backups). The data +is stored in the [`m.key_backup`](#mkey_backup) global +[account data](#client-config). + +#### Events + +{{% event event="m.key_backup" %}} + +#### Client behaviour on sign-in + +When a user signs in to a client which supports encryption and key backup: + +* If this event type exists in account data and contains the specified property + in the correct format, clients which support key backup MUST take account of + its contents in their behaviour. For example, clients may automatically turn + on/off key backup based on the property, or prompt the user, using the + property value as a default. (Because this property is server-controlled, + clients may wish to confirm the user's intention.) + +* If this event type does not exist in account data, or if it does not contain + the `enabled` property, or if the value of `enabled` is not a boolean value, + clients MUST ignore the existing value and MAY decide whether or not to + perform key backup, possibly based on user input. + +#### Client behaviour on setting change + +If the user turns on key backups, clients MUST set this event type in account +data, to `"enabled": true`. + +If the user turns off key backups, clients MUST set this event type in account +data, to `"enabled": false`. + +#### Not actively monitoring this setting + +Clients are not required to monitor the `m.key_backup` account data actively. +Clients MAY monitor the setting but should be aware that changing this setting +without user interaction based on choices made in a different client (or a +compromised homeserver) may cause unforeseen security problems or simply be +unexpected by users. diff --git a/data/api/client-server/definitions/key_backup.yaml b/data/api/client-server/definitions/key_backup.yaml new file mode 100644 index 00000000..1023b67f --- /dev/null +++ b/data/api/client-server/definitions/key_backup.yaml @@ -0,0 +1,22 @@ +# Copyright 2026 The Matrix.org Foundation C.I.C. +# +# Licensed under the Apache License, Version 2.0 (the "License"); +# you may not use this file except in compliance with the License. +# You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. + +title: Key Backup +type: object +properties: + enabled: + type: boolean + description: True if the user chose to enable key backup. False if the user chose to disable key backup. +required: + - enabled diff --git a/data/event-schemas/examples/m.key_backup.yaml b/data/event-schemas/examples/m.key_backup.yaml new file mode 100644 index 00000000..678c0ba9 --- /dev/null +++ b/data/event-schemas/examples/m.key_backup.yaml @@ -0,0 +1,7 @@ +{ + "$ref": "core/event.json", + "type": "m.key_backup", + "content": { + "enabled": false + } +} diff --git a/data/event-schemas/schema/m.key_backup.yaml b/data/event-schemas/schema/m.key_backup.yaml new file mode 100644 index 00000000..e03037ff --- /dev/null +++ b/data/event-schemas/schema/m.key_backup.yaml @@ -0,0 +1,26 @@ +{ + "$schema": "https://json-schema.org/draft/2020-12/schema", + "type": "object", + "title": "Key Backup Event", + "description": "Allows clients to track user preferences about key backup.", + "allOf": [{ + "$ref": "core-event-schema/event.yaml" + }], + "properties": { + "type": { + "type": "string", + "enum": ["m.key_backup"] + }, + "content": { + "type": "object", + "properties": { + "enabled": { + "description": "True if the user chose to enable key backup. False if the user chose to disable key backup.", + "type": "boolean", + } + }, + "required": ["enabled"] + } + }, + "required": ["type", "content"] +} From 51c049a2329e55060d3475bd359bf3c74cbe71ce Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Wed, 15 Apr 2026 11:28:34 +0100 Subject: [PATCH 02/11] Move key_backup from its own module into end_to_end_encryption.md --- content/client-server-api/_index.md | 1 - .../modules/end_to_end_encryption.md | 45 +++++++++++++++++++ .../modules/key_backup_enabled.md | 44 ------------------ 3 files changed, 45 insertions(+), 45 deletions(-) delete mode 100644 content/client-server-api/modules/key_backup_enabled.md diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md index 5d655509..dd1ca0e5 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -4386,6 +4386,5 @@ systems. {{% cs-module name="Event replacements" filename="event_replacements" %}} {{% cs-module name="Event annotations and reactions" filename="event_annotations" %}} {{% cs-module name="Recently used emoji" filename="recent_emoji" %}} -{{% cs-module name="Key backup enabled" filename="key_backup_enabled" %}} {{% cs-module name="Threading" filename="threading" %}} {{% cs-module name="Reference relations" filename="reference_relations" %}} diff --git a/content/client-server-api/modules/end_to_end_encryption.md b/content/client-server-api/modules/end_to_end_encryption.md index 1c3a82da..e470663e 100644 --- a/content/client-server-api/modules/end_to_end_encryption.md +++ b/content/client-server-api/modules/end_to_end_encryption.md @@ -1528,6 +1528,51 @@ objects described as follows: {{% definition path="api/client-server/definitions/megolm_export_session_data" %}} +###### Key backup enabled + +{{% added-in v="1.19" %}} + +This module enables clients to track a user's preference about enabling or +disabling [server-side backups of room keys](#server-side-key-backups). The data +is stored in the [`m.key_backup`](#mkey_backup) global +[account data](#client-config). + +####### Events + +{{% event event="m.key_backup" %}} + +####### Client behaviour on sign-in + +When a user signs in to a client which supports encryption and key backup: + +* If this event type exists in account data and contains the specified property + in the correct format, clients which support key backup MUST take account of + its contents in their behaviour. For example, clients may automatically turn + on/off key backup based on the property, or prompt the user, using the + property value as a default. (Because this property is server-controlled, + clients may wish to confirm the user's intention.) + +* If this event type does not exist in account data, or if it does not contain + the `enabled` property, or if the value of `enabled` is not a boolean value, + clients MUST ignore the existing value and MAY decide whether or not to + perform key backup, possibly based on user input. + +####### Client behaviour on setting change + +If the user turns on key backups, clients MUST set this event type in account +data, to `"enabled": true`. + +If the user turns off key backups, clients MUST set this event type in account +data, to `"enabled": false`. + +####### Not actively monitoring this setting + +Clients are not required to monitor the `m.key_backup` account data actively. +Clients MAY monitor the setting but should be aware that changing this setting +without user interaction based on choices made in a different client (or a +compromised homeserver) may cause unforeseen security problems or simply be +unexpected by users. + #### Messaging Algorithms ##### Messaging Algorithm Names diff --git a/content/client-server-api/modules/key_backup_enabled.md b/content/client-server-api/modules/key_backup_enabled.md deleted file mode 100644 index f0e188b3..00000000 --- a/content/client-server-api/modules/key_backup_enabled.md +++ /dev/null @@ -1,44 +0,0 @@ -### Key backup enabled - -{{% added-in v="1.19" %}} - -This module enables clients to track a user's preference about enabling or -disabling [server-side backups of room keys](#server-side-key-backups). The data -is stored in the [`m.key_backup`](#mkey_backup) global -[account data](#client-config). - -#### Events - -{{% event event="m.key_backup" %}} - -#### Client behaviour on sign-in - -When a user signs in to a client which supports encryption and key backup: - -* If this event type exists in account data and contains the specified property - in the correct format, clients which support key backup MUST take account of - its contents in their behaviour. For example, clients may automatically turn - on/off key backup based on the property, or prompt the user, using the - property value as a default. (Because this property is server-controlled, - clients may wish to confirm the user's intention.) - -* If this event type does not exist in account data, or if it does not contain - the `enabled` property, or if the value of `enabled` is not a boolean value, - clients MUST ignore the existing value and MAY decide whether or not to - perform key backup, possibly based on user input. - -#### Client behaviour on setting change - -If the user turns on key backups, clients MUST set this event type in account -data, to `"enabled": true`. - -If the user turns off key backups, clients MUST set this event type in account -data, to `"enabled": false`. - -#### Not actively monitoring this setting - -Clients are not required to monitor the `m.key_backup` account data actively. -Clients MAY monitor the setting but should be aware that changing this setting -without user interaction based on choices made in a different client (or a -compromised homeserver) may cause unforeseen security problems or simply be -unexpected by users. From da0f627c189177f9893b79dd11773cdd004bd8fb Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Wed, 15 Apr 2026 11:54:44 +0100 Subject: [PATCH 03/11] Remove module line for now-unused module. Co-authored-by: Tulir Asokan --- content/client-server-api/_index.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md index dd1ca0e5..d790c924 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -4280,7 +4280,6 @@ that profile. | [Policy Servers](#policy-servers) | Optional | Optional | Optional | Optional | Optional | | [OpenID](#openid) | Optional | Optional | Optional | Optional | Optional | | [Recently used emoji](#recently-used-emoji) | Optional | Optional | Optional | Optional | Optional | -| [Key Backup Enabled](#key-backup-enabled) | Optional | Optional | Optional | Optional | Optional | | [Reference Relations](#reference-relations) | Optional | Optional | Optional | Optional | Optional | | [Reporting Content](#reporting-content) | Optional | Optional | Optional | Optional | Optional | | [Rich replies](#rich-replies) | Optional | Optional | Optional | Optional | Optional | From 941dc8950a0737ba700c05d7ef692bee0fdabe04 Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Wed, 15 Apr 2026 11:59:01 +0100 Subject: [PATCH 04/11] Move 'Key backup enabled' into the correct section, 'Server-side key backups' --- .../modules/end_to_end_encryption.md | 90 +++++++++---------- 1 file changed, 45 insertions(+), 45 deletions(-) diff --git a/content/client-server-api/modules/end_to_end_encryption.md b/content/client-server-api/modules/end_to_end_encryption.md index e470663e..fec2cd01 100644 --- a/content/client-server-api/modules/end_to_end_encryption.md +++ b/content/client-server-api/modules/end_to_end_encryption.md @@ -1479,6 +1479,51 @@ potential new key backup algorithm version that would fix this issue. {{% http-api spec="client-server" api="key_backup" %}} +###### Key backup enabled + +{{% added-in v="1.19" %}} + +This module enables clients to track a user's preference about enabling or +disabling [server-side backups of room keys](#server-side-key-backups). The data +is stored in the [`m.key_backup`](#mkey_backup) global +[account data](#client-config). + +####### Events + +{{% event event="m.key_backup" %}} + +####### Client behaviour on sign-in + +When a user signs in to a client which supports encryption and key backup: + +* If this event type exists in account data and contains the specified property + in the correct format, clients which support key backup MUST take account of + its contents in their behaviour. For example, clients may automatically turn + on/off key backup based on the property, or prompt the user, using the + property value as a default. (Because this property is server-controlled, + clients may wish to confirm the user's intention.) + +* If this event type does not exist in account data, or if it does not contain + the `enabled` property, or if the value of `enabled` is not a boolean value, + clients MUST ignore the existing value and MAY decide whether or not to + perform key backup, possibly based on user input. + +####### Client behaviour on setting change + +If the user turns on key backups, clients MUST set this event type in account +data, to `"enabled": true`. + +If the user turns off key backups, clients MUST set this event type in account +data, to `"enabled": false`. + +####### Not actively monitoring this setting + +Clients are not required to monitor the `m.key_backup` account data actively. +Clients MAY monitor the setting but should be aware that changing this setting +without user interaction based on choices made in a different client (or a +compromised homeserver) may cause unforeseen security problems or simply be +unexpected by users. + ##### Key exports Keys can be manually exported from one device to an encrypted file, @@ -1528,51 +1573,6 @@ objects described as follows: {{% definition path="api/client-server/definitions/megolm_export_session_data" %}} -###### Key backup enabled - -{{% added-in v="1.19" %}} - -This module enables clients to track a user's preference about enabling or -disabling [server-side backups of room keys](#server-side-key-backups). The data -is stored in the [`m.key_backup`](#mkey_backup) global -[account data](#client-config). - -####### Events - -{{% event event="m.key_backup" %}} - -####### Client behaviour on sign-in - -When a user signs in to a client which supports encryption and key backup: - -* If this event type exists in account data and contains the specified property - in the correct format, clients which support key backup MUST take account of - its contents in their behaviour. For example, clients may automatically turn - on/off key backup based on the property, or prompt the user, using the - property value as a default. (Because this property is server-controlled, - clients may wish to confirm the user's intention.) - -* If this event type does not exist in account data, or if it does not contain - the `enabled` property, or if the value of `enabled` is not a boolean value, - clients MUST ignore the existing value and MAY decide whether or not to - perform key backup, possibly based on user input. - -####### Client behaviour on setting change - -If the user turns on key backups, clients MUST set this event type in account -data, to `"enabled": true`. - -If the user turns off key backups, clients MUST set this event type in account -data, to `"enabled": false`. - -####### Not actively monitoring this setting - -Clients are not required to monitor the `m.key_backup` account data actively. -Clients MAY monitor the setting but should be aware that changing this setting -without user interaction based on choices made in a different client (or a -compromised homeserver) may cause unforeseen security problems or simply be -unexpected by users. - #### Messaging Algorithms ##### Messaging Algorithm Names From c9408e804eca18019c4ea0c35e6d061fbea759b0 Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Wed, 15 Apr 2026 12:00:53 +0100 Subject: [PATCH 05/11] Remove subheadings in 'Key backup enabled' --- .../client-server-api/modules/end_to_end_encryption.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/content/client-server-api/modules/end_to_end_encryption.md b/content/client-server-api/modules/end_to_end_encryption.md index fec2cd01..56d7e75b 100644 --- a/content/client-server-api/modules/end_to_end_encryption.md +++ b/content/client-server-api/modules/end_to_end_encryption.md @@ -1488,12 +1488,8 @@ disabling [server-side backups of room keys](#server-side-key-backups). The data is stored in the [`m.key_backup`](#mkey_backup) global [account data](#client-config). -####### Events - {{% event event="m.key_backup" %}} -####### Client behaviour on sign-in - When a user signs in to a client which supports encryption and key backup: * If this event type exists in account data and contains the specified property @@ -1508,16 +1504,12 @@ When a user signs in to a client which supports encryption and key backup: clients MUST ignore the existing value and MAY decide whether or not to perform key backup, possibly based on user input. -####### Client behaviour on setting change - If the user turns on key backups, clients MUST set this event type in account data, to `"enabled": true`. If the user turns off key backups, clients MUST set this event type in account data, to `"enabled": false`. -####### Not actively monitoring this setting - Clients are not required to monitor the `m.key_backup` account data actively. Clients MAY monitor the setting but should be aware that changing this setting without user interaction based on choices made in a different client (or a From 030502f54043bf8e6fd4ae4dc501cbdbd3ef0b6f Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Wed, 15 Apr 2026 12:01:51 +0100 Subject: [PATCH 06/11] Rename 'Key backup enabled' to 'Key backup enabled preference' --- content/client-server-api/modules/end_to_end_encryption.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/client-server-api/modules/end_to_end_encryption.md b/content/client-server-api/modules/end_to_end_encryption.md index 56d7e75b..1841c03d 100644 --- a/content/client-server-api/modules/end_to_end_encryption.md +++ b/content/client-server-api/modules/end_to_end_encryption.md @@ -1479,7 +1479,7 @@ potential new key backup algorithm version that would fix this issue. {{% http-api spec="client-server" api="key_backup" %}} -###### Key backup enabled +###### Key backup enabled preference {{% added-in v="1.19" %}} From f7f6080e71a24838f9301593e7cb0cb449b0ebb8 Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Wed, 15 Apr 2026 13:56:53 +0100 Subject: [PATCH 07/11] Add link to changelog MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Kévin Commaille <76261501+zecakeh@users.noreply.github.com> --- changelogs/client_server/newsfragments/2354.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/changelogs/client_server/newsfragments/2354.feature b/changelogs/client_server/newsfragments/2354.feature index 13a56a7e..7508cc95 100644 --- a/changelogs/client_server/newsfragments/2354.feature +++ b/changelogs/client_server/newsfragments/2354.feature @@ -1 +1 @@ -Specify m.key_backup account data (MSC4287). +Specify `m.key_backup` account data, as per [MSC4287](https://github.com/matrix-org/matrix-spec-proposals/pull/4287). From b80c6238b1a9ba862b7c94e09f33210fcbbaabb7 Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Wed, 15 Apr 2026 13:57:37 +0100 Subject: [PATCH 08/11] Remove unneeded 'required' property MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Kévin Commaille <76261501+zecakeh@users.noreply.github.com> --- data/event-schemas/schema/m.key_backup.yaml | 1 - 1 file changed, 1 deletion(-) diff --git a/data/event-schemas/schema/m.key_backup.yaml b/data/event-schemas/schema/m.key_backup.yaml index e03037ff..f7bd0e0f 100644 --- a/data/event-schemas/schema/m.key_backup.yaml +++ b/data/event-schemas/schema/m.key_backup.yaml @@ -22,5 +22,4 @@ "required": ["enabled"] } }, - "required": ["type", "content"] } From 3b297cf7dafbfbb26d17cd82e073c9cb43029eac Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Wed, 15 Apr 2026 16:06:42 +0100 Subject: [PATCH 09/11] Remove the reference to a module from the key_backup section --- content/client-server-api/modules/end_to_end_encryption.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/client-server-api/modules/end_to_end_encryption.md b/content/client-server-api/modules/end_to_end_encryption.md index 1841c03d..75acd93b 100644 --- a/content/client-server-api/modules/end_to_end_encryption.md +++ b/content/client-server-api/modules/end_to_end_encryption.md @@ -1483,7 +1483,7 @@ potential new key backup algorithm version that would fix this issue. {{% added-in v="1.19" %}} -This module enables clients to track a user's preference about enabling or +This enables clients to track a user's preference about enabling or disabling [server-side backups of room keys](#server-side-key-backups). The data is stored in the [`m.key_backup`](#mkey_backup) global [account data](#client-config). From 0c557fe49ceed0b939cdf58ee922eda05c9fe974 Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Wed, 15 Apr 2026 16:17:34 +0100 Subject: [PATCH 10/11] Convert m.key_backup.yaml to yaml --- data/event-schemas/schema/m.key_backup.yaml | 49 ++++++++++----------- 1 file changed, 24 insertions(+), 25 deletions(-) diff --git a/data/event-schemas/schema/m.key_backup.yaml b/data/event-schemas/schema/m.key_backup.yaml index f7bd0e0f..5b422203 100644 --- a/data/event-schemas/schema/m.key_backup.yaml +++ b/data/event-schemas/schema/m.key_backup.yaml @@ -1,25 +1,24 @@ -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "type": "object", - "title": "Key Backup Event", - "description": "Allows clients to track user preferences about key backup.", - "allOf": [{ - "$ref": "core-event-schema/event.yaml" - }], - "properties": { - "type": { - "type": "string", - "enum": ["m.key_backup"] - }, - "content": { - "type": "object", - "properties": { - "enabled": { - "description": "True if the user chose to enable key backup. False if the user chose to disable key backup.", - "type": "boolean", - } - }, - "required": ["enabled"] - } - }, -} +--- +$schema: https://json-schema.org/draft/2020-12/schema + +allOf: + - $ref: core-event-schema/event.yaml +description: |- + Allows clients to track user preferences about key backup. +properties: + content: + type: object + properties: + enabled: + type: boolean + description: |- + True if the user chose to enable key backup. False if the user chose + to disable key backup. + required: + - enabled + type: + type: string + enum: + - m.key_backup +title: Key Backup Event +type: object From 7c1753b2088bce018c42dc1004e6b4171c66e6dc Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Thu, 16 Apr 2026 16:00:39 +0100 Subject: [PATCH 11/11] Remove unneeded extra key_backup.yaml --- .../client-server/definitions/key_backup.yaml | 22 ------------------- 1 file changed, 22 deletions(-) delete mode 100644 data/api/client-server/definitions/key_backup.yaml diff --git a/data/api/client-server/definitions/key_backup.yaml b/data/api/client-server/definitions/key_backup.yaml deleted file mode 100644 index 1023b67f..00000000 --- a/data/api/client-server/definitions/key_backup.yaml +++ /dev/null @@ -1,22 +0,0 @@ -# Copyright 2026 The Matrix.org Foundation C.I.C. -# -# Licensed under the Apache License, Version 2.0 (the "License"); -# you may not use this file except in compliance with the License. -# You may obtain a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, -# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -# See the License for the specific language governing permissions and -# limitations under the License. - -title: Key Backup -type: object -properties: - enabled: - type: boolean - description: True if the user chose to enable key backup. False if the user chose to disable key backup. -required: - - enabled