Add instructions on how to report security issues #126
+8
−0
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
|
Everyone contributing to this PR have now signed the CLA. Thanks! |
seb128
force-pushed
the
security-reporting-instructions
branch
from
0202c33
to
bf766f8
Compare
|
I've amended the commit to use my canonical email to please the CLA and forced pushed |
spydon
reviewed
Oct 3, 2024
Co-authored-by: Lukas Klingsbo <[email protected]>
spydon
approved these changes
Oct 3, 2024
sminez
approved these changes
Oct 3, 2024
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.
Quoting SEC0026 - SSDLC
The content of the file is based on the template referenced in the spec and what other Canonical repository are already using
Note that CONTRIBUTING as a similar section under 'Getting Started' which I didn't edit, we could keep it/delete it or point to the new file, any preference?