From 2e830e0dc0a8430f82866df1f680cb3c6feccd4b Mon Sep 17 00:00:00 2001 From: Michael Crosby Date: Fri, 15 Sep 2017 11:32:14 -0400 Subject: [PATCH] Update security reporting text Closes #1441 Signed-off-by: Michael Crosby --- README.md | 3 +-- RELEASES.md | 7 ++----- 2 files changed, 3 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index b7c352c29..855789cb6 100644 --- a/README.md +++ b/README.md @@ -194,8 +194,7 @@ For sync communication we have a community slack with a #containerd channel that ### Reporting security issues -__If you are reporting a security issue, please follow the responsible -disclosure guidelines and reach out discreetly at containerd-security@googlegroups.com__. +__If you are reporting a security issue, please reach out discreetly at containerd-security@googlegroups.com__. ## Copyright and license diff --git a/RELEASES.md b/RELEASES.md index 221e16615..4d159b42a 100644 --- a/RELEASES.md +++ b/RELEASES.md @@ -114,11 +114,8 @@ one of three ways: 2. Open a PR with cherry-picked change from master. 3. Open a PR with a ported fix. -__If you are reporting a security issue, please follow the responsible -disclosure guidelines and reach out discreetly__. Remember that backported PRs -must follow the versioning guidelines from this document. - -Please send security related issues to containerd-security@googlegroups.com. +__If you are reporting a security issue, please reach out discreetly at containerd-security@googlegroups.com__. +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 fairly straightforward. The steps differ depending on whether you are pulling