This bug should be just to add support for TLS_*_SHA384 ciphers in JSS.
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:
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1554056 https://bugzilla.redhat.com/show_bug.cgi?id=1554058 - Custom field type adjusted to None - Custom field version adjusted to None - Issue assigned to mharmsen
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1554056, https://bugzilla.redhat.com/show_bug.cgi?id=1554058 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1554056 https://bugzilla.redhat.com/show_bug.cgi?id=1554058)
Metadata Update from @mharmsen: - Issue set to the milestone: 4.4.2
Metadata Update from @cfu: - Issue assigned to cfu (was: mharmsen)
commit 7ca7415b54fd515b9a043b9a8b68b66f143fbffd (HEAD -> master, origin/master, origin/HEAD) Author: Christina Fu cfu@redhat.com 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
Metadata Update from @cfu: - Issue close_status updated to: fixed - Issue set to the milestone: None (was: 4.4.2) - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.