commit	8988dda41319950476ebb146df06c2e7b3fbf44d	[log] [tgz]
author	Suryakanth Sekar <suryakanth.sekar@linux.intel.com>	Thu Dec 12 21:39:14 2019 +0530
committer	Suryakanth Sekar <suryakanth.sekar@linux.intel.com>	Wed Jan 08 03:53:10 2020 +0000
tree	144f10f58f0794b87134be0ac862f92ece6e93d7
parent	2830a9cf2559c7b6956fcb5a6cce56231fcfd18e [diff]

bmcweb: Message entry for user security Event

Message entry for
BMC should detect the following intrusion or non-allowed configuration and
log the security event with description.
1. Password storing hash algo changes from SHA2-256 to MD5 in Linux pwd file
2. When any user other than root has its UID set to 0 in Linux pwd file
3. When any unsupported shells (not bash or sh) are present in Linux pwd file
4. When the root user is assigned a password in Linux password file

Tested:
1. Ran Redfish validator - passed for this new addition.

 {
  "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
  "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/75_1",
  "@odata.type": "#LogEntry.v1_4_0.LogEntry",
  "Created": "1970-01-01T00:01:15+00:00",
  "EntryType": "Event",
  "Id": "75_1",
  "Message": "weak password computing hash algorithm is enabled = MD5 Hash algorithm .",
  "MessageArgs": [
         "MD5 Hash algorithm"
     ],
  "MessageId": "OpenBMC.0.1.SecurityUserWeakHashAlgoEnabled",
  "Name": "System Event Log Entry",
  "Severity": "Critical"
 },
 {
  "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
  "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/240",
  "@odata.type": "#LogEntry.v1_4_0.LogEntry",
  "Created": "1970-01-01T00:04:00+00:00",
  "EntryType": "Event",
  "Id": "240",
  "Message": "other than /bin/bash,/bin/sh, Unsupported shell is enabled",
  "MessageArgs": [],
  "MessageId": "OpenBMC.0.1.SecurityUserUnsupportedShellEnabled",
  "Name": "System Event Log Entry",
  "Severity": "Critical"
 },
 {
  "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
  "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/246",
  "@odata.type": "#LogEntry.v1_4_0.LogEntry",
  "Created": "1970-01-01T00:04:06+00:00",
  "EntryType": "Event",
  "Id": "246",
  "Message": "Unsupported shell is removed",
  "MessageArgs": [],
  "MessageId": "OpenBMC.0.1.SecurityUserUnsupportedShellRemoved",
  "Name": "System Event Log Entry",
  "Severity": "OK"
 },

 {
  "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
  "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/604",
  "@odata.type": "#LogEntry.v1_4_0.LogEntry",
  "Created": "1970-01-01T00:10:04+00:00",
  "EntryType": "Event",
  "Id": "604",
  "Message": "password computing hash algorithm is changed to sha256/sha512.",
  "MessageArgs": [],
  "MessageId": "OpenBMC.0.1.SecurityUserHashAlgoChanged",
  "Name": "System Event Log Entry",
  "Severity": "OK"
 }
 {
 "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
 "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/75",
 "@odata.type": "#LogEntry.v1_4_0.LogEntry",
 "Created": "1970-01-01T00:01:15+00:00",
 "EntryType": "Event",
 "Id": "75",
 "Message": "root user is enabled.",
 "MessageArgs": [],
 "MessageId": "OpenBMC.0.1.SecurityUserRootEnabled",
 "Name": "System Event Log Entry",
 "Severity": "Critical"
 },
 {
 "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
 "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries/1153",
 "@odata.type": "#LogEntry.v1_4_0.LogEntry",
 "Created": "1970-01-01T00:19:13+00:00",
 "EntryType": "Event",
 "Id": "1153",
 "Message": "uid Zero is assigned with non-root user",
 "MessageArgs": [],
 "MessageId": "OpenBMC.0.1.SecurityUserNonRootUidZeroAssigned",
 "Name": "System Event Log Entry",
 "Severity": "Critical"
 }

Signed-off-by: Suryakanth Sekar <suryakanth.sekar@linux.intel.com>
Change-Id: I8a3a10be2cc85614baa7b0d2f56b3376c3301e01

redfish-core/include/registries/openbmc_message_registry.hpp[diff]

1 file changed

tree: 144f10f58f0794b87134be0ac862f92ece6e93d7

README.md

OpenBMC webserver

This component attempts to be a "do everything" embedded webserver for openbmc.

Capabilities

At this time, the webserver implements a few interfaces:

Authentication middleware that supports cookie and token based authentication, as well as CSRF prevention backed by linux PAM authentication credentials.
An (incomplete) attempt at replicating phosphor-dbus-rest interfaces in C++. Right now, a few of the endpoint definitions work as expected, but there is still a lot of work to be done. The portions of the interface that are functional are designed to work correctly for phosphor-webui, but may not yet be complete.
Replication of the rest-dbus backend interfaces to allow bmc debug to logged in users.
An initial attempt at a read-only redfish interface. Currently the redfish interface targets ServiceRoot, SessionService, AccountService, Roles, and ManagersService. Some functionality here has been shimmed to make development possible. For example, there exists only a single user role.
SSL key generation at runtime. See the configuration section for details.
Static file hosting. Currently, static files are hosted from the fixed location at /usr/share/www. This is intended to allow loose coupling with yocto projects, and allow overriding static files at build time.
Dbus-monitor over websocket. A generic endpoint that allows UIs to open a websocket and register for notification of events to avoid polling in single page applications. (this interface may be modified in the future due to security concerns.

Configuration

BMCWeb is configured by setting -D flags that correspond to options in bmcweb/CMakeLists.txt and then compiling. For example, cmake -DBMCWEB_ENABLE_KVM=NO ... followed by make. The option names become C++ preprocessor symbols that control which code is compiled into the program.

When BMCWeb starts running, it reads persistent configuration data (such as UUID and session data) from a local file. If this is not usable, it generates a new configuration.

When BMCWeb SSL support is enabled and a usable certificate is not found, it will generate a self-sign a certificate before launching the server. The keys are generated by the prime256v1 algorithm. The certificate

is issued by C=US, O=OpenBMC, CN=testhost,
is valid for 10 years,
has a random serial number, and
is signed using the SHA-256 algorithm.