From: Nancy Yuen <yuenn@google.com>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: Stewart Smith <stewart@linux.ibm.com>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: OpenBMC Security Working Group Kick Off
Date: Wed, 6 Jun 2018 15:35:04 -0700 [thread overview]
Message-ID: <CADfYTpEbEE3sbbgNFvEwrqOAX+xv8jtSGG=Trpva6=-r1OVrgw@mail.gmail.com> (raw)
In-Reply-To: <1527813505.462430.1392457368.418CFB45@webmail.messagingengine.com>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
----------
Nancy
On Thu, May 31, 2018 at 5:38 PM, Andrew Jeffery <andrew@aj.id.au> wrote:
> On Thu, 31 May 2018, at 18:08, Stewart Smith wrote:
> > Nancy Yuen <yuenn@google.com> writes:
> > > The OpenBMC Security Work Group kick off meeting is scheduled for
> Thurs May
> > > 31, 9AM PDT. This first meeting is by invite only. Please email me
> if you
> > > are interested in participating in this working group.
> >
> > Would topics like "security of the BMC from a hostile host" be part of
> > this?
>
> I vote yes, and I'm picking up the work to shut down some of the obvious
> holes again now, at least from an OpenPOWER perspective.
>
Definitely it would be a security topic for our platforms.
>
> >
> > A design of OpenPOWER systems is that the BMC and the Host don't have to
> > trust each other, and this should extend to a host that's hostile
> > towards the BMC.
> >
> > I'd be surprised if we didn't find bugs in both mboxd and host ipmi if
> > we started fuzzing those interfaces.
>
> I've have a neglected branch floating around that adds an AFL harness for
> mboxd. I should start hacking on that again :)
>
Maybe for OpenBMC Fix it next week? :D
>
> Andrew
>
[-- Attachment #2: Type: text/html, Size: 2169 bytes --]
next prev parent reply other threads:[~2018-06-06 22:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 21:04 OpenBMC Security Working Group Kick Off Nancy Yuen
2018-05-31 8:38 ` Stewart Smith
2018-05-31 19:53 ` Vernon Mauery
2018-06-01 0:38 ` Andrew Jeffery
2018-06-06 22:35 ` Nancy Yuen [this message]
2018-06-07 2:44 ` Andrew Jeffery
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='CADfYTpEbEE3sbbgNFvEwrqOAX+xv8jtSGG=Trpva6=-r1OVrgw@mail.gmail.com' \
--to=yuenn@google.com \
--cc=andrew@aj.id.au \
--cc=openbmc@lists.ozlabs.org \
--cc=stewart@linux.ibm.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).