Update Security Policy with extra security recommendations #3041
Conversation
This file contains 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.
Description
Hi, I'm Diogo from GOSST and I've created this issue and this PR to pytorch/pytorch to enhance their security policy with some security guidelines for users. As discussed in the PR with @malfet, some of the purposed guidelines fit better on pytorch/serve than on pytorch/pytorch, so I'm bringing them here to ask if they make sense to you.
As your Security Policy already have some (pretty nice) guidelines, I've adapted my suggestion to just append it to your current guidelines (you can find the original sugestion I made them in this link). If that doesn't make sense to you, please, feel free to point how it'd be a better fit.
Thanks!
Type of change
Feature/Issue validation/testing
N/A