mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-02-20 13:03:42 +01:00
f42ce28bfe
- do not use the term 'cross-signing keys' anymore: Previously, the term 'cross-signing keys' was used to refer to the master, user-signing and self-signing keys. This is not ideal since the master key is used for cross-signing but may also be used to sign the backup key, for example. In these contexts, the master key is not used for cross-signing. The term 'cross-signing keys' has therefor been replaced by 'keys used for cross-signing' or, more explicitely, by 'master, user-signing and self-signing key'. - the naming of the master key has been harmonised (no more 'master cross-signing key' or 'master signing keys'). Also the abbr. 'MSK' has been replaced by 'MK'. - in the QR code example, the term 'cross-signing key' has been replaced by 'master key' since in mode 0x00, the current user's own master key and what the device thinks the other user's master key is used. - it has been made more explicit that private keys used for cross-signing can be stored on the server are stored as described in the secrets module (as opposed to store them in unencrypted form) Signed-off-by: codedust <codedust@so.urceco.de> |
||
|---|---|---|
| .. | ||
| definitions | ||
| examples | ||
| backfill.yaml | ||
| content_repository.yaml | ||
| event_auth.yaml | ||
| events.yaml | ||
| invites-v1.yaml | ||
| invites-v2.yaml | ||
| joins-v1.yaml | ||
| joins-v2.yaml | ||
| keys_query.yaml | ||
| keys_server.yaml | ||
| knocks.yaml | ||
| leaving-v1.yaml | ||
| leaving-v2.yaml | ||
| openid.yaml | ||
| public_rooms.yaml | ||
| query.yaml | ||
| space_hierarchy.yaml | ||
| third_party_invite.yaml | ||
| transactions.yaml | ||
| user_devices.yaml | ||
| user_keys.yaml | ||
| version.yaml | ||
| wellknown.yaml | ||