| commit | 63540131ac2c2e9fa97f948c1d7a11de589e268b | [log] [tgz] |
|---|---|---|
| author | Nan Zhou <nanzhoumails@gmail.com> | Thu Nov 25 15:47:52 2021 -0800 |
| committer | Nan Zhou <nanzhoumails@gmail.com> | Wed Dec 08 22:49:04 2021 +0000 |
| tree | c3d12d6bbac1d9b6d66cc21cd365ccf74b5d4598 | |
| parent | 83e6eab0f088f742528e0860e8105340eb9dfb46 [diff] |
allow X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT This is needed when installing a server certificate with intermediate root. Due to the limitation of current implementation, the leaf certificate has to be the first certificate, followed by any intermediate root. This error is similar to the existing one with _LOCALLY. See https://security.stackexchange.com/questions/144337. Tested on QEMU. Signed-off-by: Nan Zhou <nanzhoumails@gmail.com> Change-Id: I52f3b60c5641f9421cf93a4da628f9b22e4f15d6
Certificate management allows to replace the existing certificate and private key file with another (possibly CA signed) Certificate key file. Certificate management allows the user to install both the server and client certificates.
To build this package, do the following steps:
1. ./bootstrap.sh
2. ./configure ${CONFIGURE_FLAGS}
3. make
To clean the repository run `./bootstrap.sh clean`.
Multiple instances of phosphor-certificate-manager are usually run on the bmc to support management of different types of certificates.
Usage: ./phosphor-certificate-manager [options]
Options:
--help Print this menu
--type certificate type
Valid types: client,server,authority
--endpoint d-bus endpoint
--path certificate file path
--unit=<name> Optional systemd unit need to reload
Purpose: Server https certificate
./phosphor-certificate-manager --type=server --endpoint=https \ --path=/etc/ssl/certs/https/server.pem --unit=bmcweb.service
Purpose: Client certificate validation
./phosphor-certificate-manager --type=authority --endpoint=ldap \ --path=/etc/ssl/certs/authority --unit=bmcweb.service
Purpose: LDAP client certificate validation
./phosphor-certificate-manager --type=client --endpoint=ldap \ --path=/etc/nslcd/certs/cert.pem
phosphor-certificate-manager is an implementation of the D-Bus interface defined in this document.
D-Bus service name is constructed by "xyz.openbmc_project.Certs.Manager.{Type}.{Endpoint}" and D-Bus object path is constructed by "/xyz/openbmc_project/certs/{type}/{endpoint}".
Take https certificate management as an example.
./phosphor-certificate-manager --type=server --endpoint=https \ --path=/etc/ssl/certs/https/server.pem --unit=bmcweb.service
D-Bus service name is "xyz.openbmc_project.Certs.Manager.Server.Https" and D-Bus object path is "/xyz/openbmc_project/certs/server/https".
OpenBMC bmcweb exposes various REST APIs for certificate management on the BMC, which leverages functionalities of phosphor-certificate-manager via D-Bus.