diff options
| author | Paul Moore <paul@paul-moore.com> | 2022-02-10 13:13:32 -0700 |
|---|---|---|
| committer | Tom Hromatka <tom.hromatka@oracle.com> | 2022-02-10 13:14:37 -0700 |
| commit | bc27ed0ad114fc2543dc2a782fc2c4c4c518cadc (patch) | |
| tree | 19c02b1962dd4d926c5b0be70b015ad0ab1eb18c | |
| parent | 51b50f95e1fb717e4560818f8b90b7ebde314ad1 (diff) | |
| download | libseccomp-bc27ed0ad114fc2543dc2a782fc2c4c4c518cadc.tar.gz | |
docs: consolidate security vulnerability handling in SECURITY.md
Signed-off-by: Paul Moore <paul@paul-moore.com>
Signed-off-by: Tom Hromatka <tom.hromatka@oracle.com>
[TJH: Also fixed a minor typo]
| -rw-r--r-- | doc/admin/MAINTAINER_PROCESS.md | 8 |
1 files changed, 2 insertions, 6 deletions
diff --git a/doc/admin/MAINTAINER_PROCESS.md b/doc/admin/MAINTAINER_PROCESS.md index f4d984a..8516c5a 100644 --- a/doc/admin/MAINTAINER_PROCESS.md +++ b/doc/admin/MAINTAINER_PROCESS.md @@ -47,12 +47,8 @@ the patch can be merged without a simple majority. The libseccomp vulnerability reporting process is documented in the SECURITY.md document. -The maintainers should work together with the reporter to asses the validity -and seriousness of the reported vulnerability. Whenever possible, responsible -reporting and patching practices should be followed, including notification to -the _linux-distros_ and _oss-security_ mailing lists. - -* https://oss-security.openwall.org/wiki/mailing-lists/distros +The maintainers should work together with the reporter to assess the validity +and seriousness of the reported vulnerability. ### Managing the GitHub Issue Tracker |