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

Make encrypted group operation recommendation conditional. #247

Merged
merged 2 commits into from
Mar 6, 2024
Merged

Make encrypted group operation recommendation conditional. #247

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b9e4cf5
Make encrypted group operation recommendation conditional.
Bren2010 Jan 30, 2024
3b02ba4
Update draft-ietf-mls-architecture.md
beurdouche Mar 6, 2024
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
10 changes: 6 additions & 4 deletions draft-ietf-mls-architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -899,8 +899,8 @@ delivering messages asynchronously and reliably.
## Access Control

Because all clients within a group (members) have access to the shared
cryptographic material, MLS protocol allows each member of the messaging group
to perform operations, However, every service/infrastructure has control over
cryptographic material, the MLS protocol allows each member of the messaging group
to perform operations. However, every service/infrastructure has control over
policies applied to its own clients. Applications managing MLS clients can be
configured to allow for specific group operations. On the one hand, an
application could decide that a group administrator will be the only member to
Expand All @@ -915,8 +915,10 @@ While the Application messages will always be encrypted, having the handshake
messages in plaintext has privacy consequences as someone could
collect the signatures on the handshake messages and use them for tracking.

> **RECOMMENDATION:** Prefer using encrypted group operation messages to avoid
> privacy issues related to non-encrypted signatures.
> **RECOMMENDATION:** Prefer using encrypted group operation messages unless a
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
> **RECOMMENDATION:** Prefer using encrypted group operation messages unless a
> **RECOMMENDATION:** Prefer using encrypted handshake messages unless a

> Delivery Service explicitly needs plaintext group operations to provide
beurdouche marked this conversation as resolved.
Show resolved Hide resolved
> additional features. In this case, ensure that transport-layer encryption is
> always used.

If handshake messages are encrypted, any access
control policies must be applied at the client, so the application must ensure
Expand Down
Loading