From: Ed Tanous <ed.tanous@intel.com>
To: openbmc@lists.ozlabs.org
Subject: Re: In-Band Firmware Update
Date: Mon, 6 Aug 2018 14:59:28 -0700 [thread overview]
Message-ID: <712b9342-6458-4cc4-8c59-aeb498ca5367@intel.com> (raw)
In-Reply-To: <6491f54b7b2da630cd3796c6bc3a5214@linux.vnet.ibm.com>
>
> We are going to investigate using the DFU protocol, as that
> also has host side tools already available.
>
DFU doesn't completely solve the issue though, does it? Presumably for
security reasons you can't have the DFU device exposed to the host all
the time. If you did, I'm sure the penetration testers would hit it
hard. Assuming that leaving it available all the time is a non-starter,
don't you need some command to activate the interface to allow the upload?
Assuming I'm not missing something there (I probably am) doesn't it make
more sense to just expose a USB mass storage device when the "start"
command is sent, as opposed to implementing the full DFU protocol? It
seems like that would require no utilities (aside from a simple nsh/bash
script) and be very easy to replicate.
Is there any more details on this approach?
next prev parent reply other threads:[~2018-08-06 22:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 18:13 In-Band Firmware Update Patrick Venture
2018-07-23 22:18 ` Vernon Mauery
2018-07-24 0:13 ` Sai Dasari
2018-07-24 19:02 ` Bakshi, Sachit
2018-07-24 20:38 ` Matt Spinler
2018-07-27 19:01 ` Patrick Venture
2018-08-06 16:51 ` Patrick Venture
2018-08-06 17:26 ` Patrick Venture
2018-08-06 18:36 ` Patrick Venture
2018-08-06 22:20 ` Ed Tanous
2018-08-06 23:04 ` Andrew Jeffery
2018-08-07 15:14 ` Patrick Venture
2018-08-07 16:41 ` Patrick Venture
2018-08-07 18:48 ` Patrick Venture
2018-08-07 15:11 ` Patrick Venture
2018-08-06 21:59 ` Ed Tanous [this message]
2018-08-08 1:32 ` Jeremy Kerr
2018-08-08 21:42 ` Vernon Mauery
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=712b9342-6458-4cc4-8c59-aeb498ca5367@intel.com \
--to=ed.tanous@intel.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.