Merge pull request #2503 from uhoreg/msc-fixes-2020-04

minor clarifications and corrections
pull/2510/head
Hubert Chathi 4 years ago committed by GitHub
commit 32aecc506f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -216,7 +216,7 @@ response:
}
```
Similarly, the federation endpoints `POST /user/keys/query` and `POST
Similarly, the federation endpoints `POST /user/keys/query` and `GET
/user/devices/{userId}` will include the master and self-signing keys. (It
will not include the user-signing key because it is not intended to be visible
to other users.)
@ -463,7 +463,7 @@ response:
}
```
Similarly, the federation endpoints `GET /user/keys/query` and `POST
Similarly, the federation endpoints `POST /user/keys/query` and `GET
/user/devices/{userId}` will include the new signatures for her own devices or
master key, but not signatures made by her user-signing key.

@ -66,7 +66,7 @@ corresponds to the public key.
Encrypted data is stored in the user's account_data using the event type
defined by the feature that uses the data. For example, decryption keys for
key backups could be stored under the type `m.megolm_backup.v1.recovery_key`,
key backups could be stored under the type `m.megolm_backup.v1`,
or the self-signing key for cross-signing could be stored under the type
`m.cross_signing.self_signing`.

Loading…
Cancel
Save