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 1711375 - TLS_AES_256_GCM_SHA384 is not marked as FIPS compatible
Summary: TLS_AES_256_GCM_SHA384 is not marked as FIPS compatible
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nss
Version: 8.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: 8.3
Assignee: nss-nspr-maint
QA Contact: Ivan Nikolchev
URL:
Whiteboard:
Depends On: 1809549
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-17 16:01 UTC by Alicja Kario
Modified: 2022-11-14 09:39 UTC (History)
4 users (show)

Fixed In Version: nss-3.53.1-6.el8_2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-03 13:01:31 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 1558126 0 P1 RESOLVED TLS_AES_256_GCM_SHA384 should be marked as FIPS compatible 2020-10-08 18:58:52 UTC
Red Hat Product Errata RHSA-2020:3280 0 None None None 2020-08-03 13:02:10 UTC

Description Alicja Kario 2019-05-17 16:01:38 UTC
Description of problem:
definition of TLS_AES_256_GCM_SHA384 in NSS does no specify that the cipher is FIPS compatible

Version-Release number of selected component (if applicable):
nss-3.41.0-5.el8

How reproducible:
always

Steps to Reproduce:
1. /usr/lib64/nss/unsupported-tools/listsuites
2.
3.

Actual results:
TLS_AES_128_GCM_SHA256:
  0x1301 TLS 1.3 TLS 1.3 AES-GCM  128 AEAD   Enabled  FIPS Domestic            
TLS_CHACHA20_POLY1305_SHA256:
  0x1303 TLS 1.3 TLS 1.3 CHACHA20POLY1305 256 AEAD   Enabled       Domestic            
TLS_AES_256_GCM_SHA384:
  0x1302 TLS 1.3 TLS 1.3 AES-GCM  256 AEAD   Enabled       Domestic

Expected results:
TLS_AES_128_GCM_SHA256:
  0x1301 TLS 1.3 TLS 1.3 AES-GCM  128 AEAD   Enabled  FIPS Domestic            
TLS_CHACHA20_POLY1305_SHA256:
  0x1303 TLS 1.3 TLS 1.3 CHACHA20POLY1305 256 AEAD   Enabled       Domestic            
TLS_AES_256_GCM_SHA384:
  0x1302 TLS 1.3 TLS 1.3 AES-GCM  256 AEAD   Enabled  FIPS Domestic

Additional info:

Comment 11 errata-xmlrpc 2020-08-03 13:01:31 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-2020:3280


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