commit | 02379d3572bc471ecbb75f33e5a03203c4b3e517 | [log] [tgz] |
---|---|---|
author | Ed Tanous <ed@tanous.net> | Tue Sep 15 21:15:44 2020 -0700 |
committer | Ed Tanous <ed@tanous.net> | Tue Sep 22 20:42:36 2020 +0000 |
tree | 933a6e9077cde7a16de5dcce5a85a25ce596b877 | |
parent | 684bb4b89f88b394b00b140d71c161143393f80b [diff] |
Fix IBM management console to match coding standard Lots of missing inline definitions, a case where a RVO move is not guaranteed when returning a variant, and removing the header checks, which means that these types of build errors wont happen in the future. Tested: Should be no impact, but could someone from the IBM team grab these changes and sanity check them? Signed-off-by: Ed Tanous <ed@tanous.net> Change-Id: Iea0a06b8e744542a7d08e38217718e7a969f2827
This component attempts to be a "do everything" embedded webserver for openbmc.
At this time, the webserver implements a few interfaces:
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 secp384r1
algorithm. The certificate
C=US, O=OpenBMC, CN=testhost
,SHA-256
algorithm.