All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Security Officers <security@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add security docs to SECURITY CONTACT
Date: Thu, 27 Aug 2020 15:20:16 +0200	[thread overview]
Message-ID: <20200827132016.GA4384@kozik-lap> (raw)
In-Reply-To: <20200827131827.GA546898@kroah.com>

On Thu, Aug 27, 2020 at 03:18:27PM +0200, Greg Kroah-Hartman wrote:
> On Thu, Aug 27, 2020 at 03:13:30PM +0200, Krzysztof Kozlowski wrote:
> > When changing the documents related to kernel security workflow, notify
> > the security mailing list as its concerned by this.
> > 
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> > ---
> >  MAINTAINERS | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 8107b3d5d6df..a1e07d0f3205 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -15620,6 +15620,8 @@ F:	include/uapi/linux/sed*
> >  
> >  SECURITY CONTACT
> >  M:	Security Officers <security@kernel.org>
> > +F:	Documentation/admin-guide/security-bugs.rst
> > +F:	Documentation/process/embargoed-hardware-issues.rst
> 
> The hardware-issues document is "owned" by a different group of
> suckers^Wdevelopers, that is independant of security@k.o, so that file
> shouldn't be added to them here.

True, but isn't this broader security group involved in designing and
discussing the HW security process?

Best regards,
Krzysztof


  reply	other threads:[~2020-08-27 13:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27 13:13 [PATCH] MAINTAINERS: Add security docs to SECURITY CONTACT Krzysztof Kozlowski
2020-08-27 13:18 ` Greg Kroah-Hartman
2020-08-27 13:20   ` Krzysztof Kozlowski [this message]
2020-08-27 16:07     ` Greg Kroah-Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200827132016.GA4384@kozik-lap \
    --to=krzk@kernel.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=security@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.