Return-Path: Authentication-Results: lists.ozlabs.org; spf=none (mailfrom) smtp.mailfrom=linux.intel.com (client-ip=134.134.136.20; helo=mga02.intel.com; envelope-from=richard.marian.thomaiyar@linux.intel.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=linux.intel.com Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 44NJHL270gzDqH4 for ; Tue, 19 Mar 2019 01:20:12 +1100 (AEDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Mar 2019 07:19:54 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,494,1544515200"; d="scan'208,217";a="152738144" Received: from rthomaiy-mobl2.gar.corp.intel.com (HELO [10.252.150.127]) ([10.252.150.127]) by fmsmga002.fm.intel.com with ESMTP; 18 Mar 2019 07:19:52 -0700 To: OpenBMC Maillist From: "Thomaiyar, Richard Marian" Subject: Reg default user account in OpenBMC Message-ID: <1f2c8cf9-27cf-b569-033b-9216a0a80fe8@linux.intel.com> Date: Mon, 18 Mar 2019 19:49:51 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.2 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------389392421132F8C5722F2111" Content-Language: en-US X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Mar 2019 14:20:15 -0000 This is a multi-part message in MIME format. --------------389392421132F8C5722F2111 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit All,  In OpenBMC, default password /“0penBmc” /is used for/“root” /user. This is getting applied for all recipes irrespective of companies meta-xxx layer, as this is done through phosphor-defaults.inc (under meta-phosphor distro). The only option is to override the same using local.conf.sample (but if missed, default password for root user will get applied). Currently this is not limited to DEBUG_BUILD but applied for all builds. As root user is also exposed in phosphor-user-manager, it is shown as valid user account in all the interfaces like IPMI / REDFISH / WEBUI etc. From security point of it, following recommendations are made. 1. Avoid having common default passwords across products. (i.e. it’s ok to have unique password for each device). 2. Force end-user to configure user name & password. This was also pointed out by Ed in our sync meeting - SB-327 Information Privacy – connected Devices Having said that, planning to do following. Please let me know your views / concerns / any other recommendations 1. Remove default password “0penBmc” from phosphor-defaults.inc. Any company which requires password for root user can enable the same using local.conf.sample, in its respective meta-xxx layer (Recommend to avoid using root user or in worst-case keep it for DEBUG_BUILD only) 2. Can expose different user name: openBmcUser password: 0penBmc through local.conf.sample in DEBUG_BUILD / internal builds and make sure, that this doesn’t gets applied for RELEASE version 3. Remove exposing user id 0 (root) in phosphor-user-manager. i.e. root user (uid:0) doesn’t need to be listed as user accounts in IPMI / REDFISH for all builds? (Reason: 1. As part of SELinux. 2. Few validation cases will not be covered which requires deleting all user accounts etc.). Note: If any-one really require this, then we can make it through configurable flag 4. Host interface (IPMI Commands) must be used to create user accounts in BMC (i.e. From BIOS Setup page user accounts for the BMC can be created). 5. For any systems which doesn’t have Host interface - logic can be applied to create a new user based on restrictions (say create user accounts based on certain stages – provisioning / physical presence check / can create unique password for each device etc.) Regards, Richard --------------389392421132F8C5722F2111 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

All,

 In OpenBMC, default password “0penBmc” is used for “root” user. This is getting applied for all recipes irrespective of companies meta-xxx layer, as this is done through phosphor-defaults.inc (under meta-phosphor distro). The only option is to override the same using local.conf.sample (but if missed, default password for root user will get applied).  Currently this is not limited to DEBUG_BUILD but applied for all builds. As root user is also exposed in phosphor-user-manager, it is shown as valid user account in all the interfaces like IPMI / REDFISH / WEBUI etc. From security point of it, following recommendations are made.

1. Avoid having common default passwords across products. (i.e. it’s ok to have unique password for each device).

2. Force end-user to configure user name & password.

This was also pointed out by Ed in our sync meeting - SB-327 Information Privacy – connected Devices


Having said that, planning to do following. Please let me know your views / concerns / any other recommendations

1. Remove default password “0penBmc” from phosphor-defaults.inc. Any company which requires password for root user can enable the same using local.conf.sample, in its respective meta-xxx layer (Recommend to avoid using root user or in worst-case keep it for DEBUG_BUILD only)

2. Can expose different user name: openBmcUser password: 0penBmc through local.conf.sample in DEBUG_BUILD / internal builds and make sure, that this doesn’t gets applied for RELEASE version

3. Remove exposing user id 0 (root) in phosphor-user-manager. i.e. root user (uid:0) doesn’t need to be listed as user accounts in IPMI / REDFISH for all builds? (Reason: 1. As part of SELinux.  2. Few validation cases will not be covered which requires deleting all user accounts etc.). Note: If any-one really require this, then we can make it through configurable flag

4. Host interface (IPMI Commands) must be used to create user accounts in BMC (i.e. From BIOS Setup page user accounts for the BMC can be created).

5. For any systems which doesn’t have Host interface - logic can be applied to create a new user based on restrictions (say create user accounts based on certain stages – provisioning / physical presence check / can create unique password for each device etc.)


Regards,

Richard

--------------389392421132F8C5722F2111--