Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
It was determined that certain SHA384 FIPS ciphers should be enabled by default for RSA:
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
and the following SHA384 FIPS ciphers should be enabled by default for ECC:
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
Reference: Bug 1554055 - Permit certain SHA384 FIPS ciphers to be enabled by default for RSA and ECC . . .
Created attachment 1455410[details]
This patch adds support to TLS_*_SHA384 ciphers
This patch adds support to TLS_*_SHA384 ciphers.
It also adds an optional test that for specific ciphers in tests/SSLClientAuth.java.
Comment on attachment 1455410[details]
This patch adds support to TLS_*_SHA384 ciphers
Looks good and everything makes sense. Also there is some new test code.
commit 82f4b9a032f942fdc005e12a408c8e87c9ea0f36 (HEAD -> JSS_4_4_BRANCH)
Author: Christina Fu <cfu>
Date: Thu Jun 28 17:42:36 2018 -0700
Ticket #4 Add support for TLS_*_SHA384 ciphers
This patch adds support for TLS_*_SHA384 ciphers.
Fixes https://pagure.io/jss/issue/4
test procedure:
follow instruction in testSpecificCiphers() of
jss/org/mozilla/jss/tests/SSLClientAuth.java
compile and test per instruction in
jss/README
I tested this Bugzilla on the version: 10.5.9-5.el7
To test this Bugzilla I followed the steps which I used to verify Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1596769#
It working as expected.
Verifying this Bugzilla
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/RHBA-2018:3188
It was determined that certain SHA384 FIPS ciphers should be enabled by default for RSA: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 TLS_RSA_WITH_AES_256_GCM_SHA384 and the following SHA384 FIPS ciphers should be enabled by default for ECC: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 Reference: Bug 1554055 - Permit certain SHA384 FIPS ciphers to be enabled by default for RSA and ECC . . .