commit | cb6cb49df6778d48ef3a90d181169abfb4e4354e | [log] [tgz] |
---|---|---|
author | James Feist <james.feist@linux.intel.com> | Fri Apr 03 13:36:17 2020 -0700 |
committer | James Feist <james.feist@linux.intel.com> | Tue Apr 07 22:26:23 2020 +0000 |
tree | 133c9b0a117b6d420c48fee9e41f3926306cfafd | |
parent | ab6554f1d8197753cfb430a72798dde6f4461552 [diff] |
Protect against timer exhaustion Currently there is no check to see if all timers are used. This adds a check so that under many connections we don't get a double free. Tested: Spun up many connections and double free went away Change-Id: I7c6914f566064c57ad28d3bfe79a53e44f598a35 Signed-off-by: James Feist <james.feist@linux.intel.com>
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.