-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add initial security policy #5886
Conversation
Signed-off-by: Morgan Tocker <[email protected]>
Signed-off-by: Morgan Tocker <[email protected]>
Signed-off-by: Morgan Tocker <[email protected]>
SECURITY.md
Outdated
|
||
#### Policy for supported releases | ||
|
||
If a security vulnerability affects supported branches (i.e. Vitess 5), then a Fix Lead will be appointed and the full security process as defined below will apply. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would remove the ( i.e. ) here. and change this to
If a security vulnerability affects currently supported branches
to prevent people from think Vitess 5 is a forever supported branch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed in e29d8f1 but there are a couple of places that needed to be updated. Please check to confirm!
Signed-off-by: Morgan Tocker <[email protected]>
Fixes #5739
This is based on the Envoy security policy, with some simplifications for what I think makes sense for Vitess:
Feedback welcome of course!
Signed-off-by: Morgan Tocker [email protected]