commit | c6bfcfc2f0038735d48e1fdaef40e0788f00cef7 | [log] [tgz] |
---|---|---|
author | Manojkiran Eda <manojkiran.eda@gmail.com> | Sun Jun 14 10:44:11 2020 +0530 |
committer | ManojKiran Eda <manojkiran.eda@gmail.com> | Fri Jun 19 03:37:05 2020 +0000 |
tree | 05c8558260ae685707dde1eb1bd730d98540d3f2 | |
parent | 67a78d8758859a4e4477de932d24fac5fb287dad [diff] |
Migrate to boost 1.73 - Poky already had moved to 1.73, and bmcweb is lagging behind. - There are lot of improvements in 1.73(especially better support for c++20 standard) that can be leveraged by developer community, so migrating the dependency boost library to 1.73 Tested By: - Compiled in all sdks, and unit tests passed. Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com> Change-Id: Ia1c53bb3c96151d41c18b67a6d0c82edb756e7fd
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.