#3049 Installation does use proper signing algorithm when creating temporary SSL server certificate
Closed: migrated by dmoluguw. Opened by rcritten.

The FUTURE crypto policy in F29 requires RSA keys >= 3072 and signature alg >= 384.

During spawn a temporary certificate is issued for the SSL server cert using certutil which fails:

ERROR ....... subprocess.CalledProcessError: Command '['certutil', '-S', '-d', '/etc/pki/pki-tomcat/alias', '-h', 'internal', '-n', 'Server-Cert cert-pki-ca', '-s', 'cn=ipa.example.test,o=2018-08-16 08:23:54', '-k', 'rsa', '-g', '4096', '-m', '0', '-v', '12', '-c', 'cn=ipa.example.test,o=2018-08-16 08:23:54', '-t', 'CTu,CTu,CTu', '-z', '/etc/pki/pki-tomcat/ca/noise', '-f', '/etc/pki/pki-tomcat/pfile', '-x']' returned non-zero exit status 255.!

I ran this manually and got:

certutil -S -d /etc/pki/pki-tomcat/alias -h internal -n 'Server-Cert cert-pki-ca' -s cn=ipa.example.test,o=2018-08-16 08:23:54 -k rsa -g 4096 -m 0 -v 12 -c cn=ipa.example.test,o=2018-08-16 08:23:54 -t CTu,CTu,CTu -z /etc/pki/pki-tomcat/ca/noise -f /etc/pki/pki-tomcat/pfile -x

Generating key. This may take a few moments...

certutil: bad certificate request
SEC_ERROR_CERT_SIGNATURE_ALGORITHM_DISABLED: The certificate was signed using a signature algorithm that is disabled because it is not secure.
certutil: unable to create cert (The certificate was signed using a signature algorithm that is disabled because it is not secure.)

So I tried again and specified the signing algorithm using -Z SHA512 and it succeeded.


Metadata Update from @mharmsen:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/3167

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

Metadata