[Skiboot] [PATCH 00/11] MBOX Protocol: Onwards to V3
stewart at linux.vnet.ibm.com
Mon Jul 17 16:38:23 AEST 2017
Patrick Williams <patrick at stwcx.xyz> writes:
> On Mon, Jul 03, 2017 at 02:04:08PM +1000, Suraj Jitindar Singh wrote:
>> On Mon, 2017-07-03 at 09:15 +1000, Cyril Bur wrote:
>> > On Fri, 2017-06-30 at 12:16 -0500, Patrick Williams wrote:
>> > > On Thu, Jun 29, 2017 at 10:39:14PM +1000, Cyril Bur wrote:
>> > > > Then on to actually implementing V3 - at the time of writing V2
>> > > > Suraj
>> > > > did suggest what has become patch 8. This actually makes the V3
>> > > > patch
>> > > > - patch 9 very easy.
>> > >
>> > > Where are the public discussions of a v3 protocol taking place? I
>> > > haven't seen any background on it until you and Suraj dropped code
>> > > into
>> > > various repositories.
>> > >
>> > Well then lets have a discussion.
>> If we agree that a discussion needs to take place is it something we
>> can do here on the mailing list or do you think we need a call or
>> something more formal?
> Please start with an email both to this and the openbmc list with a
> summary of what you are trying to accomplish and why. I don't know who
> asked for this, who intends to use it, and most importantly, what the
> requirements are. Any "discussion" I attempt to have at this stage is
> simply conjecture based on what the code appears to be doing.
It came from a discussion of "how hard would it be to implement lockable
flash through mbox, and could we work around some issues of not having
lockable flash by doing this."
Specifically, protecting the secure boot keystore (at least against
fat-fingering and accidentally bricking your machine) and being able to
have a petitboot password that couldn't be cleared by the host.
OPAL Architect, IBM.
More information about the Skiboot