Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add advice about when to change sender keys #167

Merged
merged 1 commit into from
Dec 1, 2023
Merged

Add advice about when to change sender keys #167

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions draft-ietf-sframe-enc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -677,6 +677,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
Loading