Bug 1859298

Summary:	[RFE] Support ECDSA private keys for TLS
Product:	Red Hat Enterprise Linux 9	Reporter:	mreynolds
Component:	389-ds-base	Assignee:	Pierre Rogier <progier>
Status:	CLOSED ERRATA	QA Contact:	LDAP QA Team <idm-ds-qe-bugs>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	9.0	CC:	atolani, bsmejkal, emartyny, idm-ds-dev-bugs, pasik, pcech, progier, spichugi, tbordaz, tmihinto, vashirov
Target Milestone:	beta	Keywords:	FutureFeature, Reopened, Triaged
Target Release:	9.1	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sync-to-jira
Fixed In Version:	389-ds-base-2.2.4-1.el9	Doc Type:	Enhancement
Doc Text:	Feature: Support certificates using elliptic curves Reason: ECDSA is a stronger cryptographic algorithm than RSA and some commercial certificate authority relies on it. Result: Now certificate using either ECDSA or RSA keys are supported.	Story Points:	---
Clone Of:
Clones:	2096795 (view as bug list)		Environment:
Last Closed:	2023-05-09 07:41:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2096795

Description mreynolds 2020-07-21 16:16:27 UTC

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.

Comment 3 RHEL Program Management 2022-01-21 07:27:14 UTC

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.

Comment 17 bsmejkal 2022-12-12 11:35:07 UTC

As per comment #c15, marking as VERIFIED.

Comment 18 Evgenia Martynyuk 2023-02-27 14:18:21 UTC

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

Comment 19 Pierre Rogier 2023-02-27 14:28:24 UTC

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

Comment 21 errata-xmlrpc 2023-05-09 07:41:32 UTC

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