OpenBMC Image Management

Stewart Smith stewart at linux.vnet.ibm.com
Mon Jan 30 16:54:40 AEDT 2017


Adriana Kobylak <anoo at linux.vnet.ibm.com> writes:
> BMC:
> *Save multiple firmware versions, starting with 2, to provide the
> ability to roll-back if needed. If single BMC chip system, save both
> versions there. If two BMC chip system, save other version in 2nd
> chip.

two pnor chip or two bmc chips?

with this, is there a mitiigation for downgrade attacks?

> * Implement various levels of ‘persistency’, such as dev, factory,
> field. Dev persistency would allow for local patches (/usr/local/ for
> example) that can be cleared before shipping to customers. Factory
> mode could delete the location where user data such as network
> settings resides but preserves the mac address and uuid for
> example. Etc.

patches to what?

-- 
Stewart Smith
OPAL Architect, IBM.



More information about the openbmc mailing list