Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-certificate-manager / 811a29e1941db0157f49d2e05491be945f7b2f07
commit811a29e1941db0157f49d2e05491be945f7b2f07[log] [tgz]
authorNidhin MS <nidhin.ms@intel.com>Thu May 13 12:54:32 2021 +0530
committerNidhin MS <nidhin.ms@intel.com>Thu May 20 12:46:20 2021 +0530
tree25861e3014371172560ee712359ad5c88ddd3320
parentdc91fb61e5056d0ee508caf0356ff44e735f11e2 [diff]
Verify that certificate is loadable in SSL context

Openssl requires private keys to have a minimum keylength specified by
openssl security level 1. As a result RSA keys shorter
than 1024 bits and ECC keys shorter than 160 bits are prohibited. Add a
validation step to create an SSL context and try to load the
certificate.

Tested:
Tested RSA with length 512 756 and 1024

Change-Id: Idac4dea6279964bfd8e3d996d91cd278678c73f9
Signed-off-by: Nidhin MS <nidhin.ms@intel.com>
1 file changed
tree: 25861e3014371172560ee712359ad5c88ddd3320
  1. bmc-vmi-ca/
  2. test/
  3. .clang-format
  4. .gitignore
  5. .lcovrc
  6. argument.cpp
  7. argument.hpp
  8. bootstrap.sh
  9. certificate.cpp
  10. certificate.hpp
  11. certs_manager.cpp
  12. certs_manager.hpp
  13. configure.ac
  14. csr.cpp
  15. csr.hpp
  16. LICENSE
  17. mainapp.cpp
  18. MAINTAINERS
  19. Makefile.am
  20. Makefile.am.include
  21. README.md
  22. watch.cpp
  23. watch.hpp
README.md

phosphor-certificate-manager

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

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`.

To Run

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

Https certificate management

Purpose: Server https certificate

./phosphor-certificate-manager --type=server --endpoint=https \
    --path=/etc/ssl/certs/https/server.pem --unit=bmcweb.service

CA certificate management

Purpose: Client certificate validation

./phosphor-certificate-manager --type=authority --endpoint=ldap \
    --path=/etc/ssl/certs/authority --unit=bmcweb.service

LDAP client certificate management

Purpose: LDAP client certificate validation

./phosphor-certificate-manager --type=client --endpoint=ldap \
    --path=/etc/nslcd/certs/cert.pem

D-Bus Interface

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".

Usage in openbmc/bmcweb

OpenBMC bmcweb exposes various REST APIs for certificate management on the BMC, which leverages functionalities of phosphor-certificate-manager via D-Bus.