Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-03-03 10:14:10 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

change version from string to integer, plus other minor improvements

Browse source
This commit is contained in:
Hubert Chathi 2018-10-19 22:19:55 -04:00
parent de5120335f
commit b45416e8b0
1 changed files with 8 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
proposals/1219-storing-megolm-keys-serverside.md
View file

@ -139,7 +139,7 @@ Example:
On success, returns a JSON object with keys: On success, returns a JSON object with keys:
- `version` (integer): the backup version - `version` (string): the backup version
##### `GET /room_keys/version/{version}` ##### `GET /room_keys/version/{version}`
@ -152,7 +152,7 @@ On success, returns a JSON object with keys:
/room_keys/version`. /room_keys/version`.
- `auth_data` (object): Required. Same as in the body parameters for - `auth_data` (object): Required. Same as in the body parameters for
`POST /room_keys/version`. `POST /room_keys/version`.
- `version` (integer): Required. The backup version. - `version` (string): Required. The backup version.
Error codes: Error codes:
@ -275,9 +275,6 @@ The JSON object is then encrypted by generating an ephemeral curve25519 key,
performing an ECDH with the ephemeral key and the backup's public key to performing an ECDH with the ephemeral key and the backup's public key to
generate an AES key, and encrypting the stringified object using AES. generate an AES key, and encrypting the stringified object using AES.
Tradeoffs
---------
Security Considerations Security Considerations
----------------------- -----------------------
@ -286,7 +283,8 @@ key backup. This proposal does not attempt to protect against that.
An attacker who gains access to a user's account can create a new backup An attacker who gains access to a user's account can create a new backup
version using a key that they control. For this reason, clients SHOULD confirm version using a key that they control. For this reason, clients SHOULD confirm
with users before sending keys to a new backup version. with users before sending keys to a new backup version or verify that it was
created by a trusted device by checking the signature.
Other Issues Other Issues
------------ ------------
@ -299,3 +297,7 @@ backup requests randomly.
Conclusion Conclusion
---------- ----------
This proposal allows users to securely and conveniently back up and restore
their decryption keys so that users logging into a new device can decrypt old
messages.