You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
matrix-spec/data/api/server-server/definitions/event-schemas
codedust f42ce28bfe Clarify terminology for keys in cross-signing module
- 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>
5 months ago
..
m.device_list_update.yaml Fix enum types in JSON schemas (#1634) 2 years ago
m.direct_to_device.yaml Use `patternProperties` in more places with supported formats (#1813) 2 years ago
m.presence.yaml Fix enum types in JSON schemas (#1634) 2 years ago
m.receipt.yaml Use `patternProperties` in more places with supported formats (#1813) 2 years ago
m.signing_key_update.yaml Clarify terminology for keys in cross-signing module 5 months ago
m.typing.yaml Fix enum types in JSON schemas (#1634) 2 years ago