add some e2ee clarifications
This commit is contained in:
parent
1cdfbd3cd8
commit
fbbf3b81c5
4 changed files with 29 additions and 9 deletions
|
@ -3,9 +3,9 @@ allOf:
|
|||
- $ref: core-event-schema/event.yaml
|
||||
|
||||
description: |-
|
||||
This event type is used to forward keys for end-to-end encryption. Typically
|
||||
it is encrypted as an `m.room.encrypted` event, then sent as a [to-device](/client-server-api/#send-to-device-messaging)
|
||||
event.
|
||||
This event type is used to forward keys for end-to-end encryption.
|
||||
It is encrypted as an `m.room.encrypted` event using [Olm](#molmv1curve25519-aes-sha2),
|
||||
then sent as a [to-device](/client-server-api/#send-to-device-messaging) event.
|
||||
properties:
|
||||
content:
|
||||
properties:
|
||||
|
|
|
@ -3,8 +3,9 @@ allOf:
|
|||
- $ref: core-event-schema/event.yaml
|
||||
|
||||
description: |-
|
||||
This event type is used to exchange keys for end-to-end encryption. Typically
|
||||
it is encrypted as an `m.room.encrypted` event, then sent as a [to-device](/client-server-api/#send-to-device-messaging) event.
|
||||
This event type is used to exchange keys for end-to-end encryption.
|
||||
It is encrypted as an `m.room.encrypted` event using [Olm](#molmv1curve25519-aes-sha2),
|
||||
then sent as a [to-device](/client-server-api/#send-to-device-messaging) event.
|
||||
properties:
|
||||
content:
|
||||
properties:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue