| commit | db029c9521a394b65f5ae18be4735213ef51a269 | [log] [tgz] |
|---|---|---|
| author | Kowalski, Kamil <kamil.kowalski@intel.com> | Mon Jul 08 17:09:39 2019 +0200 |
| committer | Zbigniew Kurzynski <zbigniew.kurzynski@intel.com> | Mon Nov 04 08:33:06 2019 +0000 |
| tree | f6e67d89dce15ee6a0bcf3afb5eff5048453e007 | |
| parent | 06a69d7b0674857ebe708025c17ce2fca93e1bf0 [diff] |
Support uploading multiple certificates per authority service. This request is a proposition of extending current mode=authority with support for multiple certificates instead of single one. This review addresses also this issue: https://github.com/openbmc/phosphor-certificate-manager/issues/3 but with a restriction to mode=authority. Other modes still operates on a single certification file. New mode requires that user provides directory path instead of certificate path as --path argument if using --type=authority. Tested: - Manually tested Install, Remove and Replace paths for existing modes to confirm no change of behavior occurs (authority, client, server) - Manually tested Install, Remove and Replace paths for authority mode to confirm that it behaves as expected i.e. filename is changed on certificate replacement that mirrors change in certificate hash - Confirmed no regression in unit tests Change-Id: Icd33723c1fc2580679aaaf54b3e99dfb09342402 Signed-off-by: Kowalski, Kamil <kamil.kowalski@intel.com> Signed-off-by: Zbigniew Kurzynski <zbigniew.kurzynski@intel.com>
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`.