Rob Crittenden 02e19d0a39 Add SHA384withRSA as a certificate signing algorithm ... It required support in dogtag which was added in 10.5.0. This is only easily configurable during installation because it will set ca.signing.defaultSigningAlgorithm to the selected algorithm in CS.cfg The certificate profiles will generally by default set default.params.signingAlg=- which means use the CA default. So while an existing installation will technically allow SHA384withRSA it will require profile changes and/or changing the defaultSigningAlgorithm in CS.cfg and restarting (completely untested). And that won't affect already issued-certificates. https://pagure.io/freeipa/issue/8906 Signed-off-by: Rob Crittenden <rcritten@redhat.com> Reviewed-By: Florence Blanc-Renaud <frenaud@redhat.com>		2021-07-09 13:21:00 -04:00
..
caIPAserviceCert_mal.cfg.tmpl	Add SHA384withRSA as a certificate signing algorithm	2021-07-09 13:21:00 -04:00
caIPAserviceCert_mod_mal.cfg.tmpl	Add SHA384withRSA as a certificate signing algorithm	2021-07-09 13:21:00 -04:00
caIPAserviceCert_mod.cfg.tmpl	Add SHA384withRSA as a certificate signing algorithm	2021-07-09 13:21:00 -04:00
caIPAserviceCert.xml.tmpl	Add SHA384withRSA as a certificate signing algorithm	2021-07-09 13:21:00 -04:00
smime-mod.cfg.tmpl	Add SHA384withRSA as a certificate signing algorithm	2021-07-09 13:21:00 -04:00
smime.cfg.tmpl	Add SHA384withRSA as a certificate signing algorithm	2021-07-09 13:21:00 -04:00
usercert-priv-key.pem	ipatests: CA ACL - added config templates	2015-10-27 09:57:48 +01:00
usercert.conf.tmpl	ipatests: remove ipacertbase option from test CSR configuration	2016-07-12 10:55:50 +02:00