Skip to content

Commit

Permalink
Merge pull request #167 from sframe-wg/sender-key-advice
Browse files Browse the repository at this point in the history
Add advice about when to change sender keys
  • Loading branch information
bifurcation authored Dec 1, 2023
2 parents b8c663a + 50bdf9c commit dbd448a
Showing 1 changed file with 9 additions and 0 deletions.
9 changes: 9 additions & 0 deletions draft-ietf-sframe-enc.md
Original file line number Diff line number Diff line change
Expand Up @@ -681,6 +681,15 @@ If a new participant joins mid-call, they will need to receive from each sender
sender. Evicting a participant requires each sender to send a fresh sender key
to all receivers.

It is up to the application to decide when sender keys are updated. A sender
key may be updated by sending a new `base_key` (updating the key generation) or
by hashing the current `base_key` (updating the ratchet step). Ratcheting the
key forward is useful when adding new receivers to an SFrame-based interaction,
since it assures that the new receivers can't decrypt any media encrypted before
they were added. If a sender wishes to assure the opposite property when
removing a receiver (i.e., ensuring that the receiver can't decrypt media after
they are removed), then the sender will need to distribute a new sender key.

## MLS

The Messaging Layer Security (MLS) protocol provides group authenticated key
Expand Down

0 comments on commit dbd448a

Please sign in to comment.