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

Make encrypted group operation recommendation conditional. #247

Merged
merged 2 commits into from
Mar 6, 2024

Conversation

Bren2010
Copy link
Contributor

No description provided.

@ekr
Copy link
Collaborator

ekr commented Jan 30, 2024

As noted in the discussion about issue #246, I don't think this is the right answer.

@@ -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

Copy link
Contributor

@rohanmahy rohanmahy left a comment

Choose a reason for hiding this comment

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

If we go with this PR, I prefer using "handshake" messages as Raphael suggests.

@beurdouche beurdouche merged commit a8fe837 into mlswg:main Mar 6, 2024
1 check passed
@beurdouche
Copy link
Member

That is what we actually discussed at the interim... Thanks for the PR.

@ekr
Copy link
Collaborator

ekr commented Mar 6, 2024

Please back this out. There wasn't a consensus call on the list, so we shouldn't be landing anything until that happens.

@seanturner
Copy link
Contributor

Yeah we should back this out. I'll set something up to finalize this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

6 participants