docs: Add extra security instructions

Update to point to containerd/project documentation that lists a new
way to report a security vulnerability on Github directly.

Signed-off-by: Danny Canter <danny@dcantah.dev>
This commit is contained in:
Danny Canter 2022-12-01 04:59:31 -08:00
parent ae6c244995
commit 39cc684c6a
2 changed files with 5 additions and 2 deletions

View File

@ -328,7 +328,7 @@ A third party security audit was performed by Cure53 in 4Q2018; the [full report
### Reporting security issues ### Reporting security issues
__If you are reporting a security issue, please reach out discreetly at security@containerd.io__. Please follow the instructions at [containerd/project](https://github.com/containerd/project/blob/main/SECURITY.md#reporting-a-vulnerability)
## Licenses ## Licenses

View File

@ -164,7 +164,10 @@ one of three ways:
2. Open a PR with cherry-picked change from main. 2. Open a PR with cherry-picked change from main.
3. Open a PR with a ported fix. 3. Open a PR with a ported fix.
__If you are reporting a security issue, please reach out discreetly at security@containerd.io__. __If you are reporting a security issue:__
Please follow the instructions at [containerd/project](https://github.com/containerd/project/blob/main/SECURITY.md#reporting-a-vulnerability)
Remember that backported PRs must follow the versioning guidelines from this document. Remember that backported PRs must follow the versioning guidelines from this document.
Any release that is "active" can accept backports. Opening a backport PR is Any release that is "active" can accept backports. Opening a backport PR is