#264 Route vulnerability reports to private advisory link - #272
Open
VasilevNStas wants to merge 2 commits into
Open
#264 Route vulnerability reports to private advisory link#272VasilevNStas wants to merge 2 commits into
VasilevNStas wants to merge 2 commits into
Conversation
SECURITY.md told reporters to open a public issue, which defeats the purpose. Replaced with GitHub's private security advisory link.
- Add language specifier to fenced code block (MD040) - Use 1-prefix for all ordered list items (MD029) - Fix table pipe spacing (MD060) - Break long table line under 80 chars (MD013)
Contributor
Author
|
@yegor256 plz review |
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
1 participant
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.
SECURITY.md instructed reporters to open a public GitHub issue, which immediately discloses the vulnerability to everyone watching the repo and to search engines.
Fixed by pointing to the private security advisory form at
/security/advisories/new.Fixes #264