From 639d1bdd623429ed9e4eed96aa0ba53604f684e0 Mon Sep 17 00:00:00 2001 From: Stephen J Day Date: Thu, 19 Oct 2017 13:34:55 +0200 Subject: [PATCH] README, RELEASES: update security email Signed-off-by: Stephen J Day --- README.md | 2 +- RELEASES.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 46df58e76..28635dbf0 100644 --- a/README.md +++ b/README.md @@ -196,7 +196,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 reach out discreetly at containerd-security@googlegroups.com__. +__If you are reporting a security issue, please reach out discreetly at security@containerd.io__. ## Copyright and license diff --git a/RELEASES.md b/RELEASES.md index ca09d9854..a5f02425b 100644 --- a/RELEASES.md +++ b/RELEASES.md @@ -114,7 +114,7 @@ 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 reach out discreetly at containerd-security@googlegroups.com__. +__If you are reporting a security issue, please reach out discreetly at security@containerd.io__. 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