Steps to Reproduce:
1. Setup directory server. 2. Install ca subsystem with ECC.
Actual results:
# pkispawn -s CA -f ecc_ca.cfg Log file: /var/log/pki/pki-ca-spawn.20171218005026.log Loading deployment configuration from ecc_ca.cfg. Installing CA into /var/lib/pki/ECC_RootCA. pkispawn : ERROR ....... subprocess.CalledProcessError: Command '['certutil', '-R', '-d', '/opt/ECC_RootCA/ca/alias', '-s', u'cn=PKI Administrator,e=caadmin@idm.lab.eng.rdu.redhat.com,ou=ECC_RootCA,o=example.com Security Domain', '-k', 'ec', '-q', '2048', '-z', '/opt/ECC_RootCA/ca/alias/noise', '-f', '/opt/ECC_RootCA/ca/password.conf', '-o', '/opt/ECC_RootCA/ca/alias/admin_pkcs10.bin']' returned non-zero exit status 255! Installation failed: Command '['certutil', '-R', '-d', '/opt/ECC_RootCA/ca/alias', '-s', u'cn=PKI Administrator,e=caadmin@example.com,ou=ECC_RootCA,o=example.com Security Domain', '-k', 'ec', '-q', '2048', '-z', '/opt/ECC_RootCA/ca/alias/noise', '-f', '/opt/ECC_RootCA/ca/password.conf', '-o', '/opt/ECC_RootCA/ca/alias/admin_pkcs10.bin']' returned non-zero exit status 255
Expected results:
Installation should be successful.
Additional info:
While we specifying the key type as 'ecc' then it should be expected to take a nistp* algorithms, instead, it is taking '2048' as a length. I faced this issue because of the `pki_admin_keysize` and `pki_admin_key_size` parameter. In the config file, if you specify `pki_admin_key_size` instead of `pki_admin_keysize` it will fail, but it will work with `pki_admin_keysize` with ECC. In the pki deployer code[1], it is clearly mentioned that if the key size for ECC is not specified then it should take the default 'nistp256' size. If you do not specify the key size for ECC then it takes 2048 as a key size. [1] https://github.com/dogtagpki/pki/blob/master/base/server/python/pki/server/deployment/pkihelper.py#L2599
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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1526881 - Custom field type adjusted to None - Custom field version adjusted to None
commit 96a3bb4dddb3d18af5ddc917e02c437175dcfee7 Author: Matthew Harmsen mharmsen@redhat.com Date: Thu Jan 18 15:53:27 2018 -0700
Fixed setup of ECC CA Restored ECC functionality that was lost during 'Refactoring SSL server cert creation' (https://pagure.io/dogtagpki/issue/2786). Additionally, to avoid confusion, deprecated 'pki_admin_keysize' and use 'pki_admin_key_size' to make parameters consistent across different certificate key types. Fixes: https://pagure.io/dogtagpki/issue/2887 Change-Id: I1206b37a00b7da5e30fef5b2d12fb266e2779cfb
Metadata Update from @mharmsen: - Issue close_status updated to: fixed - Issue set to the milestone: 10.5.4 (was: 10.5) - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.5.4-1.fc27
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/3005
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.