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.
Bug 1432907 - Cipher suite mismatch with latest nss
Summary: Cipher suite mismatch with latest nss
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openldap
Version: 7.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Matus Honek
QA Contact: Patrik Kis
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-16 11:26 UTC by Patrik Kis
Modified: 2017-08-01 20:19 UTC (History)
3 users (show)

Fixed In Version: openldap-2.4.44-4.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 20:19:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1852 0 normal SHIPPED_LIVE Moderate: openldap security, bug fix, and enhancement update 2017-08-01 18:22:49 UTC

Description Patrik Kis 2017-03-16 11:26:51 UTC 
Description of problem:
Openldap does not ask for TLS_AES.*GCM cipher suites in client hello while the latest nss supports these suites.

Version-Release number of selected component (if applicable):
openldap-2.4.44-1.el7.x86_64
nss-3.28.3-3.el7.x86_64

How reproducible:
always

Steps to Reproduce:

openssl req -x509 -newkey rsa -keyout localhost.key -out localhost.crt -nodes -batch
tshark -i lo -f "port 4433"  -o 'ssl.desegment_ssl_records:TRUE' -V -d tcp.port==4433,ssl &>capture.txt &
openssl s_server -accept 4433 -key localhost.key -cert localhost.crt -www 2> /dev/null > /dev/null &
ldapsearch -d -1 -H ldaps://localhost:4433/

# kill the s_server and tshark and check the results


Actual results:
# grep TLS_AES.*GCM capture.txt 


Expected results:
# grep TLS_AES.*GCM capture.txt 
TLS_AES_128_GCM_SHA256
TLS_AES_256_GCM_SHA384


Additional info:

The latest nss-3.28.3-3.el7 supports these suites:

/usr/lib64/nss/unsupported-tools/listsuites |grep -v 'suites:' | sed ':a;/:$/{N;s/\\n//;ba}' | grep -v SSL2 |grep TLS_AES.*GCM
TLS_AES_128_GCM_SHA256:
TLS_AES_256_GCM_SHA384:
Comment 2 Patrik Kis 2017-03-16 11:31:57 UTC 
One important step to the reproducer:

echo -e "TLS_CIPHER_SUITE ALL\n" > ~/.ldaprc
Comment 3 Patrik Kis 2017-03-16 14:32:43 UTC 
Another issue discovered that was caused by updated nss is with the default cipher suites. The following suites are missing from client hello sent:

-TLS_AES_128_GCM_SHA256
-TLS_CHACHA20_POLY1305_SHA256
-TLS_AES_256_GCM_SHA384
-TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
-TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
-TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256


The reproducer is the same as above, just add 'TLS_CIPHER_SUITE DEFAULT' or nothing to ~/.ldaprc.

rm -f ~/.ldaprc
openssl req -x509 -newkey rsa -keyout localhost.key -out localhost.crt -nodes -batch
tshark -i lo -f "port 4433"  -o 'ssl.desegment_ssl_records:TRUE' -V -d tcp.port==4433,ssl &>capture.txt &
openssl s_server -accept 4433 -key localhost.key -cert localhost.crt -www 2> /dev/null > /dev/null &
ldapsearch -d -1 -H ldaps://localhost:4433/


grep -A 100 'Client Hello' capture.txt | grep -o 'TLS_\w*' > client_hello.suites

/usr/lib64/nss/unsupported-tools/listsuites | grep -v 'suites:' | sed ':a;/:$/{N;s/\n//;ba}' | grep Enabled | grep -o '^[^:]*' > default.suites


diff default.suites client_hello.suites 28,33d27
< TLS_AES_128_GCM_SHA256
< TLS_CHACHA20_POLY1305_SHA256
< TLS_AES_256_GCM_SHA384
< TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
< TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
< TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256
Comment 5 Hubert Kario 2017-03-17 10:46:46 UTC 
(In reply to Patrik Kis from comment #3)
> Another issue discovered that was caused by updated nss is with the default
> cipher suites. The following suites are missing from client hello sent:
> 
> -TLS_AES_128_GCM_SHA256
> -TLS_CHACHA20_POLY1305_SHA256
> -TLS_AES_256_GCM_SHA384

Those are expected to be missing: those are TLSv1.3 cipihersuites and we are not enabling TLSv1.3 in NSS in RHEL just yet - tlsv1.3 is not yet finished.

> -TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
> -TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
> -TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256

Note that openldap will need sff rating for those ciphers - those are 256 bit ciphers.
Comment 19 errata-xmlrpc 2017-08-01 20:19: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, 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/RHSA-2017:1852
Note You need to log in before you can comment on or make changes to this bug.