Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1852634 [details]
pkispawn-ecc-sub-ca-log.txt provided by awnuk

Hi Andrew, I tried creating an ECC subCA with pkispawn single step and it seems to work just fine (and QE did as well for both single and tw-step).
I understand that if I had the time to look closely at your scripts I might be able to debug and  find out what you did differently.  However, I am tied up at the moment.

What I could do now is to provide you with the pkispawn files that I used to create the root CA and the subCA for you to play with and perhaps check against your scripts, if you are okay with it.
Let me know if that would work for you. thanks.

Created attachment 1852635 [details]
cfu's pkispawn file for creating root ca

This was how I ran it:
pkispawn -v -f ca-ecc.inf -s CA

Created attachment 1852636 [details]
cfu's pkispawn file for create subordinate ca

I ran like the following:
pkispawn -v -f subca-ec.inf -s CA

https://bugzilla.redhat.com/show_bug.cgi?id=2018608#c22 - should provide steps to reproduce this case.

Hi Christina,
Hi Matt,

I'm glad to inform you that ECC subCA issue is fixed. You may close this ticket as fixed.

I didn't have to change anything on my side, so I would assume that there were some nss/jss updates that appeared on CentOS side a bit later.

Thanks again for all the help.
Andrew