commit | 26fb83eff52ccab4f26b64a99324b5b3daf4f1c1 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Tue Dec 14 14:08:28 2021 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Tue Dec 14 15:26:15 2021 -0600 |
tree | 1f86e0b7726b36edad56d48a89fc7397467a7e44 | |
parent | 55ceaa2b975c455383ba3266b7cdaf644abba462 [diff] |
certs_manager: switch keygen to support openssl-3 Many of the functions currently used to generate key pairs are deprecated in OpenSSL-3. Update keygen functions to use non-deprecated functions. Unfortunately, the replacement functions are not available in OpenSSL-1, so we have to add an #ifdef block around the proper routines for each version. Tested: Ran test cases under both OpenSSL1 and OpenSSL3. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I888a8a796cc97caf8c402cd546ab39b4931960ed
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.