LKML Archive on lore.kernel.org
 help / color / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Kees Cook <keescook@chromium.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Tyler Hicks <tyhicks@canonical.com>,
	Ben Hutchings <ben@decadent.org.uk>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Jiri Kosina <jkosina@suse.cz>, Matt Linton <amuse@google.com>,
	Matthew Garrett <mjg59@google.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation/process: Add Google contact for embargoed hardware issues
Date: Wed, 4 Sep 2019 10:25:58 -0700
Message-ID: <20190904172558.GA24934@roeck-us.net> (raw)
In-Reply-To: <201909040922.56496BF70@keescook>

On Wed, Sep 04, 2019 at 09:24:49AM -0700, Kees Cook wrote:
> This adds myself as the Google contact for embargoed hardware security
> issues and fixes some small typos.
> 
> Cc: Guenter Roeck <linux@roeck-us.net>
> Cc: Matt Linton <amuse@google.com>
> Cc: Matthew Garrett <mjg59@google.com>
> Signed-off-by: Kees Cook <keescook@chromium.org>

Acked-by: Guenter Roeck <groeck@chromium.org>

> ---
>  Documentation/process/embargoed-hardware-issues.rst | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst
> index d37cbc502936..1c1ad684d753 100644
> --- a/Documentation/process/embargoed-hardware-issues.rst
> +++ b/Documentation/process/embargoed-hardware-issues.rst
> @@ -5,7 +5,7 @@ Scope
>  -----
>  
>  Hardware issues which result in security problems are a different category
> -of security bugs than pure software bugs which  only affect the Linux
> +of security bugs than pure software bugs which only affect the Linux
>  kernel.
>  
>  Hardware issues like Meltdown, Spectre, L1TF etc. must be treated
> @@ -159,7 +159,7 @@ Mitigation development
>  
>  The initial response team sets up an encrypted mailing-list or repurposes
>  an existing one if appropriate. The disclosing party should provide a list
> -of contacts for all other parties who have already been, or should be
> +of contacts for all other parties who have already been, or should be,
>  informed about the issue. The response team contacts these parties so they
>  can name experts who should be subscribed to the mailing-list.
>  
> @@ -230,8 +230,8 @@ an involved disclosed party. The current ambassadors list:
>    SUSE		Jiri Kosina <jkosina@suse.cz>
>  
>    Amazon
> -  Google
> -  ============== ========================================================
> +  Google	Kees Cook <keescook@chromium.org>
> +  ============= ========================================================
>  
>  If you want your organization to be added to the ambassadors list, please
>  contact the hardware security team. The nominated ambassador has to
> -- 
> 2.17.1
> 
> 
> -- 
> Kees Cook

      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04 16:24 Kees Cook
2019-09-04 17:25 ` Guenter Roeck [this message]

Reply instructions:

You may reply publically 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=20190904172558.GA24934@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=amuse@google.com \
    --cc=ben@decadent.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=jkosina@suse.cz \
    --cc=jpoimboe@redhat.com \
    --cc=keescook@chromium.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@google.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --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

LKML Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git
	git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git
	git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git
	git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git
	git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git
	git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git
	git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git
	git clone --mirror https://lore.kernel.org/lkml/7 lkml/git/7.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \
		linux-kernel@vger.kernel.org
	public-inbox-index lkml

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git