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.

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

Address comments from Yoav Nir and Rohan Mahy. Fixes #263 #264

Merged
merged 2 commits into from
Aug 3, 2024
Merged
Changes from all commits
Commits
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
15 changes: 8 additions & 7 deletions draft-ietf-mls-architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -1418,12 +1418,13 @@ MLS provides additional protection regarding secrecy of past messages and future
messages. These cryptographic security properties are Forward Secrecy (FS) and
Post-Compromise Security (PCS).

FS means that access to all encrypted traffic history combined with access to
all current keying material on clients will not defeat the secrecy properties of
messages older than the oldest key of the compromised client. Note that this
means that clients have the extremely important role of deleting appropriate
keys as soon as they have been used with the expected message, otherwise the
secrecy of the messages and the security for MLS is considerably weakened.
FS means that access to all encrypted traffic history combined with
access to all current keying material on clients will not defeat the
secrecy properties of messages older than the oldest key of the
compromised client. Note that this means that clients have to delete the appropriate
keys as soon as they have been used with the expected message,
otherwise the secrecy of the messages and the security for MLS is
considerably weakened.

PCS means that if a group member's state is compromised at some time t1 but the
group member subsequently performs an update at some time t2, then all MLS
Expand Down Expand Up @@ -1967,7 +1968,7 @@ and identities. If the signature keys are reused across groups, the adversary
can get more information about the targeted user.

> **RECOMMENDATION:** Ensure that linking between public keys and identities
> only happens in expected scenarios. Otherwise privilege a stronger separation.
> only happens in expected scenarios.

## Considerations for attacks outside of the threat model

Expand Down
Loading