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.

This bug has been copied from bug #1554056 and has been proposed to be backported to 7.5 z-stream (EUS).

commit 82f4b9a032f942fdc005e12a408c8e87c9ea0f36 (HEAD -> JSS_4_4_BRANCH, origin/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 per instruction here: https://bugzilla.redhat.com/show_bug.cgi?id=1554056#c7

Hey Christina,

I verified https://bugzilla.redhat.com/show_bug.cgi?id=1597180#c6 and it works fine, do you think I need to do some extra test steps for this BZ or is it sufficient?

(In reply to Amol K from comment #5)
> Hey Christina,
> 
> I verified https://bugzilla.redhat.com/show_bug.cgi?id=1597180#c6 and it
> works fine, do you think I need to do some extra test steps for this BZ or
> is it sufficient?

I think if you followed the provided test procedure then it should be good.

The Tomcatjss one (https://bugzilla.redhat.com/show_bug.cgi?id=1596769 ) should give this fix more test.

I tested this BZ on 10.5.1-14.el7_5, and it is working as expected.

I followed the same steps which are mentioned in the BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1596769#c6

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:2453