Reword our security policy#42953
Merged
Merged
Conversation
In ac24cd6 we started asking for people to use **private** github security reports, but kept the wording from before, which was related to accepting such reports as **public** issues. The wording doesn't make sense in the context of asking people for private reports, so update the wording to reflect that. Signed-off-by: Jonathan Schwender <[email protected]>
servo-highfive
added
the
S-awaiting-review
Member
Author
|
IMHO it would also make sense to accept security reports via email (Security of email is obviously an issue, but given the scenario and TLS being common, it's probably acceptable and many other projects do accept security reports via email without requiring E2E encryption). |
mrego
approved these changes
Mar 2, 2026
servo-highfive
removed
the
S-awaiting-review
servo-highfive
added
the
S-awaiting-merge
servo-highfive
removed
the
S-awaiting-merge
simonwuelker
added a commit
to simonwuelker/servo
that referenced
this pull request
Mar 2, 2026
{"fail_fast": false, "matrix": [{"name": "Linux (WPT)", "workflow": "linux", "wpt": true, "profile": "release", "unit_tests": false, "build_libservo": false, "bencher": false, "coverage": false, "build_args": "", "wpt_args": "", "number_of_wpt_chunks": 20}]}
simonwuelker
pushed a commit
to simonwuelker/servo
that referenced
this pull request
Mar 3, 2026
In ac24cd6 we started asking for people to use **private** github security reports, but kept the wording from before, which was related to accepting such reports as **public** issues. The wording doesn't make sense in the context of asking people for private reports, so update the wording to reflect that. This is not a policy change, just making the wording more clear. Testing: Not required, policy description. Signed-off-by: Jonathan Schwender <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In ac24cd6 we started asking for people to use private github security reports, but kept the wording from before, which was related to accepting such reports as public issues.
The wording doesn't make sense in the context of asking people for private reports, so update the wording to reflect that.
This is not a policy change, just making the wording more clear.
Testing: Not required, policy description.