Default root password: 2.4 vs. 2.6

Thomaiyar, Richard Marian richard.marian.thomaiyar at linux.intel.com
Fri Mar 15 18:11:36 AEDT 2019


Hi Dave,

you should be able to override it in your local.conf.sample, please make 
sure you are using append and correct image name


(in local.conf.sample)

INHERIT += "extrausers"

EXTRA_USERS_PARAMS_append_pn-obmc-phosphor-image  = " \

usermod -p '\$1\$UGMqyqdG\$FZiylVFmRRfl9Z0Ue8G7e/' root; \

"

or add your own image name (instead of obmc-phosphor-image after 
append_pn) for which you are building. With this it will override.

Let me know if you are facing any problem with this method.


regards,

Richard


On 3/15/2019 12:05 AM, David Thompson wrote:
>
> When we transitioned our OpenBMC baseline from 2.4 to 2.6
>
> we noticed that the default root password for our platform has
>
> changed to “0penBmc”.  This appears to come from the file:
>
> meta-phosphor/conf/distro/include/phosphor-defaults.inc:
>
> /usermod -p '\$1\$UGMqyqdG\$FZiylVFmRRfl9Z0Ue8G7e/' root;/
>
> And this password setting overrides the password we had chosen
>
> in our machine’s local.conf.sample.    We experimented but could not
>
> find a way to prevent this override behavior.
>
> Is this the intent with this change in 2.6 that all platforms by default
>
> have root password of “0penBmc”?  Is there a way to have a platform
>
> specific root password without changing “phosphor-defaults.inc”?
>
> Regards,
>
> Dave
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20190315/f30ba05f/attachment.htm>


More information about the openbmc mailing list