Skip to content

Conversation

@codedust
Copy link
Contributor

Closely related to the 'Security Considerations' section introduced in #4199, and in order to improve the overal privacy aspects of Matrix during the design process, this introduces a 'Privacy Considerations' section in the proposal template, referencing the privacy threats, threat mitigation strategies and guidelines described in RFC 6973.

Closely related to the 'Security Considerations' section introduced in
matrix-org#4199,
and in order to improve the overal privacy aspects of Matrix during the design
process, this introduces a 'Privacy Considerations' section in the proposal
template, referencing the privacy threats, threat mitigation strategies and
guidelines described in
[RFC 6973](https://datatracker.ietf.org/doc/html/rfc6973).

Signed-off-by: codedust <[email protected]>
Copy link
Member

@turt2live turt2live left a comment

Choose a reason for hiding this comment

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

This may require an MSC to change the process here, as it's not immediately clear to me that this should be required (but should be strong recommended). Security Considerations becoming required was discussed among SCT members prior to the PR, making acceptance easier.

I feel this needs more discussion, which an MSC would provide.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants