Searched hist:aaf3206f (Results 1 – 3 of 3) sorted by relevance
/openbmc/bmcweb/ |
H A D | README.md | aaf3206f Mon Mar 09 12:41:31 CDT 2020 Vernon Mauery <vernon.mauery@linux.intel.com> Change the default EC key to secp384r1 prime256v1 is okay for now, but secp384r1 is more future-proof (gives us a couple more years) and in this case does not really have any drawbacks. Tested: Checked to see that a new secp384r1 key is generated on first boot and the generate CSR redfish option works. Change-Id: I334fc56db3dd55058a4c6780f8966bcc48d8f816 Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com>
|
/openbmc/bmcweb/include/ |
H A D | ssl_key_handler.hpp | aaf3206f Mon Mar 09 12:41:31 CDT 2020 Vernon Mauery <vernon.mauery@linux.intel.com> Change the default EC key to secp384r1 prime256v1 is okay for now, but secp384r1 is more future-proof (gives us a couple more years) and in this case does not really have any drawbacks. Tested: Checked to see that a new secp384r1 key is generated on first boot and the generate CSR redfish option works. Change-Id: I334fc56db3dd55058a4c6780f8966bcc48d8f816 Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com>
|
/openbmc/bmcweb/redfish-core/lib/ |
H A D | certificate_service.hpp | aaf3206f Mon Mar 09 12:41:31 CDT 2020 Vernon Mauery <vernon.mauery@linux.intel.com> Change the default EC key to secp384r1 prime256v1 is okay for now, but secp384r1 is more future-proof (gives us a couple more years) and in this case does not really have any drawbacks. Tested: Checked to see that a new secp384r1 key is generated on first boot and the generate CSR redfish option works. Change-Id: I334fc56db3dd55058a4c6780f8966bcc48d8f816 Signed-off-by: Vernon Mauery <vernon.mauery@linux.intel.com>
|