commit | ad0006e4500f349beb425a7d5b21feac685bdb9f | [log] [tgz] |
---|---|---|
author | Ed Tanous <edtanous@google.com> | Tue May 11 15:55:47 2021 -0700 |
committer | Ed Tanous <ed@tanous.net> | Wed May 12 19:50:58 2021 +0000 |
tree | d0771ab2c411dcb9ce63fd286f1d7898764f3e49 | |
parent | 1b1be67fb8d50293d452316f51227363750a3d00 [diff] |
Make OpenSSLGenerator max() and min() constexpr The latest version of gcc seems to be enforcing that these are static and constexpr, presumably because std::random_device is now using them in a constexpr context. It seems odd this would be required (you'd think it would be breaking backward compatibility) but it's an easy enough change to make. Tested: Only tested that code builds. Not tested functionally. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: I3f5e7077d56178fbc7b4e02f4e2f4a357c928c5b
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/meson_options.txt
and then compiling. For example, meson <builddir> -Dkvm=disabled ...
followed by ninja
in build directory. The option names become C++ preprocessor symbols that control which code is compiled into the program.
meson builddir ninja -C builddir
meson builddir -Dbuildtype=minsize -Db_lto=true -Dtests=disabled ninja -C buildir
If any of the dependencies are not found on the host system during configuration, meson automatically gets them via its wrap dependencies mentioned in bmcweb/subprojects
.
meson builddir -Dwrap_mode=nofallback ninja -C builddir
meson builddir -Db_coverage=true -Dtests=enabled ninja coverage -C builddir test
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.