From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
security@kernel.org, linux-doc@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Jiri Kosina <jkosina@suse.com>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Laura Abbott <labbott@redhat.com>,
Ben Hutchings <ben@decadent.org.uk>,
Tyler Hicks <tyhicks@canonical.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Jiri Kosina <jkosina@suse.cz>
Subject: Re: [PATCH v2] Documentation/admin-guide: Embargoed hardware security issues
Date: Tue, 20 Aug 2019 09:58:50 -0500 [thread overview]
Message-ID: <20190820145850.x445rw4uoqz6n4hw@treble> (raw)
In-Reply-To: <20190815212505.GC12041@kroah.com>
On Thu, Aug 15, 2019 at 11:25:05PM +0200, Greg Kroah-Hartman wrote:
> +Contact
> +-------
> +
> +The Linux kernel hardware security team is separate from the regular Linux
> +kernel security team.
> +
> +The team only handles the coordination of embargoed hardware security
> +issues. Reports of pure software security bugs in the Linux kernel are not
> +handled by this team and the reporter will be guided to contact the regular
> +Linux kernel security team (:ref:`Documentation/admin-guide/
> +<securitybugs>`) instead.
> +
> +The team can be contacted by email at <hardware-security@kernel.org>. This
> +is a private list of security officers who will help you to coordinate an
> +issue according to our documented process.
> +
> +The list is encrypted and email to the list can be sent by either PGP or
> +S/MIME encrypted and must be signed with the reporter's PGP key or S/MIME
> +certificate. The list's PGP key and S/MIME certificate are available from
> +https://www.kernel.org/....
This link needs to be filled in?
> +Encrypted mailing-lists
> +-----------------------
> +
> +We use encrypted mailing-lists for communication. The operating principle
> +of these lists is that email sent to the list is encrypted either with the
> +list's PGP key or with the list's S/MIME certificate. The mailing-list
> +software decrypts the email and re-encrypts it individually for each
> +subscriber with the subscriber's PGP key or S/MIME certificate. Details
> +about the mailing-list software and the setup which is used to ensure the
> +security of the lists and protection of the data can be found here:
> +https://www.kernel.org/....
Ditto?
--
Josh
next prev parent reply other threads:[~2019-08-20 14:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 13:01 [PATCH] Documentation/admin-guide: Embargoed hardware security issues Greg Kroah-Hartman
2019-07-25 21:13 ` Jonathan Corbet
2019-07-26 14:47 ` Thomas Gleixner
2019-08-15 21:20 ` Greg Kroah-Hartman
2019-08-15 22:12 ` Randy Dunlap
2019-08-15 22:31 ` Greg Kroah-Hartman
2019-08-15 23:10 ` Randy Dunlap
2019-08-02 4:49 ` Willy Tarreau
2019-08-02 6:57 ` Greg Kroah-Hartman
2019-08-02 9:24 ` Willy Tarreau
2019-08-04 0:17 ` Jiri Kosina
2019-08-04 0:21 ` Jiri Kosina
2019-08-05 14:40 ` Eric W. Biederman
2019-08-05 14:59 ` Greg Kroah-Hartman
2019-08-05 15:12 ` Greg Kroah-Hartman
2019-08-15 21:04 ` Greg Kroah-Hartman
2019-08-15 21:25 ` [PATCH v2] " Greg Kroah-Hartman
2019-08-15 22:15 ` Randy Dunlap
2019-08-15 22:31 ` Greg Kroah-Hartman
2019-08-20 14:58 ` Josh Poimboeuf [this message]
2019-08-20 16:58 ` 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=20190820145850.x445rw4uoqz6n4hw@treble \
--to=jpoimboe@redhat.com \
--cc=ben@decadent.org.uk \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.com \
--cc=jkosina@suse.cz \
--cc=konrad.wilk@oracle.com \
--cc=labbott@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=security@kernel.org \
--cc=tglx@linutronix.de \
--cc=tyhicks@canonical.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).