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.

This bug is created as a clone of upstream ticket:
https://pagure.io/389-ds-base/issue/50010

#### Issue Description
Support ECDSA private keys. This is both:

* Pure ECDSA
* Mixed RSA + ECDSA support

How this looks today is unknown. However, it doesn't work given:

```
/opt/dirsrv/sbin/ns-slapd -d 0 -D /opt/dirsrv/etc/dirsrv/slapd-localhost 
Assertion failure: ((*privkey)->keyType) == rsaKey, at /home/william/development/389ds/ds/ldap/servers/slapd/ssl.c:2893
[1]    12717 abort      /opt/dirsrv/sbin/ns-slapd -d 0 -D /opt/dirsrv/etc/dirsrv/slapd-localhost


```

This is important as it blocks us from using strong future proof cryptographic mechanisms in TLS.

This may be of interest to @mhonek.

Important would be establishment of a ECDSA type in the nss_ssl.py module so we can test this properly and programmatically.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

As per comment #c15, marking as VERIFIED.

Hi Pierre!

I have prepared the Doc Text field for this BZ. Could you please review it:



.Now Directory Server supports ECDSA private keys for TLS.

Previously, Directory server supported only RSA keys. As a conscience, you could not use a stronger cryptographic algorithm for protection of the Directory Server connections. 
With this update, you can use both ECDSA or RSA private keys to secure Directory Server.  


Thanks, 
Evgenia

Hi Evgenia,
I think that you meant "As a consequence" instead of "As a conscience"
Except that point, it feels good.
Regards,
  Pierre

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (389-ds-base bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2274