From: Nancy Yuen <yuenn@google.com>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: Brad Bishop <bradleyb@fuzziesquirrel.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Secure boot for BMC
Date: Mon, 11 Feb 2019 16:30:12 -0800 [thread overview]
Message-ID: <CADfYTpENfKyyoMuhuN+RzD7nCQbo+g8sWS-mxMU0PUS5C-Z3yw@mail.gmail.com> (raw)
In-Reply-To: <1549861046.1162750.1655235472.36317B95@webmail.messagingengine.com>
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
We are working on secure boot, but we have a requirement for a Google HW
root of trust so I'm not sure if that fits in with these discussions.
----------
Nancy
On Sun, Feb 10, 2019 at 8:57 PM Andrew Jeffery <andrew@aj.id.au> wrote:
> On Wed, 6 Feb 2019, at 00:44, Brad Bishop wrote:
> > Hi everyone
> >
> > Does anyone have plans to provide a secure BMC boot implementation to
> > OpenBMC in the 2.7 or 2.8 timeframe? Just trying to get a feel for who
> > all wants to collaborate on this before I submit a design template.
> >
> > thx - brad
>
> I'm interested in secureboot discussions.
>
> Andrew
>
[-- Attachment #2: Type: text/html, Size: 1059 bytes --]
next prev parent reply other threads:[~2019-02-12 0:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 14:14 Secure boot for BMC Brad Bishop
2019-02-05 15:05 ` Teddy Reed
2019-02-05 20:14 ` Supreeth Venkatesh
2019-02-07 1:44 ` Joel Stanley
2019-02-07 2:03 ` Ryan Chen
2019-02-07 18:39 ` Vijay Khemka
2019-02-07 5:06 ` Luke Chen
2019-02-07 21:55 ` Vernon Mauery
2019-02-11 4:57 ` Andrew Jeffery
2019-02-12 0:30 ` Nancy Yuen [this message]
2019-02-12 23:13 ` Andrew Jeffery
2019-02-14 0:34 ` Joseph Reynolds
2019-02-14 23:19 ` Andrew Jeffery
2019-02-18 16:54 ` Avi Fishman
2019-02-12 3:32 ` Ratan Gupta
2019-02-12 13:58 ` George Keishing
2019-02-18 19:27 ` Brad Bishop
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=CADfYTpENfKyyoMuhuN+RzD7nCQbo+g8sWS-mxMU0PUS5C-Z3yw@mail.gmail.com \
--to=yuenn@google.com \
--cc=andrew@aj.id.au \
--cc=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.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.