Repository navigation
Replace Microsoft's security policy with this fork's - #30
Merged
Merged
Conversation
SECURITY.md sent vulnerability reports to the Microsoft Security Response Center, which no longer handles cpprestsdk. Ask reporters to use GitHub's private vulnerability reporting for this repository instead, and say which versions get security fixes. Signed-off-by: Gareth Sylvester-Bradley <garethsb@nvidia.com>
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
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.mdwas Microsoft's standard policy. It sent vulnerability reports to the Microsoft Security Response Center, which no longer handles cpprestsdk now that Microsoft has archived the repository.The new policy asks reporters to use GitHub's private vulnerability reporting, which is now enabled for this repository. It says that security fixes go to the default branch and its next release, and that vulnerabilities in dependencies such as OpenSSL should go to those projects.
The policy names the "Report a vulnerability" button on the Security tab and the default branch, rather than a URL or a branch name, so it stays correct if the repository moves to an organization.
Co-authored-by: Gareth's 🤖 buddy