All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stewart Smith <stewart@linux.ibm.com>
To: Adriana Kobylak <anoo@linux.ibm.com>,
	Joseph Reynolds <jrey@linux.ibm.com>
Cc: openbmc <openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org>,
	Openbmc <openbmc@lists.ozlabs.org>, "Thomaiyar\,
	Richard Marian" <richard.marian.thomaiyar@linux.intel.com>
Subject: Re: Move away from default password
Date: Tue, 18 Jun 2019 08:58:02 +1000	[thread overview]
Message-ID: <871rzr6cqt.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <67d4cc41211749ef9ff888a31d9e8615@linux.vnet.ibm.com>

Adriana Kobylak <anoo@linux.ibm.com> writes:
>>> 1. Unique password per BMC.
>>> In this approach, there is a way to change the factory default 
>>> password.  Example flow: assemble the BMC, test it, factory reset, 
>>> generate unique password (such as `pwgen`), then use a new function 
>>> “save factory default settings” which would save the current 
>>> setting into a new “factory settings” flash partition. After that, 
>>> a factory reset would reset to the factory installed password, not to 
>>> the setting in the source code.
>
> How would this new "factory settings" flash partition be protected 
> against being modified by an unauthorized or malicious user?

My guess would be it'd be protected the same way that the default
password is today: not at all. If an attacker can write to flash, the
only way to reset the box is to dediprog the BMC flash chip.

-- 
Stewart Smith
OPAL Architect, IBM.

  reply	other threads:[~2019-06-17 22:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 16:46 Move away from default password Joseph Reynolds
2019-06-17 18:01 ` Thomaiyar, Richard Marian
2019-06-17 18:41   ` Adriana Kobylak
2019-06-17 22:58     ` Stewart Smith [this message]
2019-06-20 16:00       ` Joseph Reynolds
2019-06-17 22:56 ` Stewart Smith
2019-06-20 15:46   ` Joseph Reynolds
2019-06-20 23:12     ` Stewart Smith
  -- strict thread matches above, loose matches on Subject: below --
2019-06-20  7:55 Carter Su(苏孝)
2019-06-20 15:30 ` Joseph Reynolds
2019-06-20 22:38 ` Stewart Smith

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=871rzr6cqt.fsf@linux.vnet.ibm.com \
    --to=stewart@linux.ibm.com \
    --cc=anoo@linux.ibm.com \
    --cc=jrey@linux.ibm.com \
    --cc=openbmc-bounces+anoo=linux.ibm.com@lists.ozlabs.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=richard.marian.thomaiyar@linux.intel.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 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.