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 1667568 - x25519 allowed in FIPS mode
Summary: x25519 allowed in FIPS mode
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nss
Version: 8.1
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: rc
: 8.0
Assignee: nss-nspr-maint
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On: 1679667 1694603
Blocks: 1669180 1701002 1728260 1754518
TreeView+ depends on / blocked
 
Reported: 2019-01-18 20:44 UTC by Alex Scheel
Modified: 2019-09-23 13:13 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1669180 1728260 1754518 (view as bug list)
Environment:
Last Closed: 2019-08-05 08:14:35 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 1521578 0 -- RESOLVED x25519 support in pk11pars.c 2020-09-03 09:27:54 UTC

Description Alex Scheel 2019-01-18 20:44:31 UTC
Description of problem:

In NSS, Curve25519 lacks a configuration parameter in the pkcs11.txt configuration format. As x25519 isn't yet an approved FIPS curve (with only the 3 NIST curves being approved), x25519 should not be enabled in FIPS mode; however, because it lacks a parameter, config="disable=ALL allow=<whitelist>" will fail to blacklist x25519.


On RHEL 7, this can be reproduced with the following since curl links against NSS:

1. Add an explicit config="disable=Curve25519" to /etc/pki/nssdb/pkcs11.txt
2. tcpdump -i eth0 -w capture.pcap
3. curl https://google.com

Notice how the Client Hello has x25519 as a supported group in the Client Hello. However, if you instead specify "SECP256R1" as the disabled curve, it will correctly disappear from the Client Hello.


This bug applies to RHEL7, RHEL8, RHEL8.1, and Fedora 29 as well. I believe a relevant portion showing the omission of x25519 is here:

https://github.com/nss-dev/nss/blob/master/lib/pk11wrap/pk11pars.c#L197


I was told to file this bug against RHEL 8.1 though. 




Version-Release number of selected component (if applicable):

nss-3.36.0-7.el7_5.x86_64

to

nss-3.41.0-1.fc29.x86_64



Expected results:

x25519 shouldn't be negotiated as a known group in FIPS mode. Configuration (whether crypto-policies on RHEL8/Fedora or pkcs11.txt) should understand x25519.


Note You need to log in before you can comment on or make changes to this bug.