#2952 Permit additional FIPS ciphers to be enabled by default for RSA . . .
Closed: fixed 4 years ago Opened 4 years ago by mharmsen.

It was determined that the following additional FIPS ciphers should be enabled by default for RSA:

  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
  • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA

Reference: dogtagpki Pagure Issue #2855 - restrict default cipher suite to those ciphers permitted in fips mode


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=1550786
- Custom field type adjusted to None
- Custom field version adjusted to None

4 years ago

The contents of this bug was divided and filed as:

dogtagpki Pagure Issue #2952 - Permit certain SHA384 FIPS ciphers to be enabled by default for RSA and ECC . . .

Author: Matthew Harmsen mharmsen@redhat.com
Date: Mon Mar 5 18:33:51 2018 -0700

Permit additional FIPS ciphers to be enabled by default for RSA . . .

It was determined that the following additional FIPS ciphers should be
enabled by default for RSA:

    * TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
    * TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
    * TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
    * TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA

Reference: dogtagpki Pagure Issue #2855 - restrict default cipher suite to
           those ciphers permitted in fips mode

Fixes: https://pagure.io/dogtagpki/issue/2952
Change-Id: I0947e8581beb3140e4c07800dd2c6bc9d90a6cd8

Metadata Update from @mharmsen:
- Issue close_status updated to: fixed
- Issue set to the milestone: 10.5.7 (was: 10.5)
- Issue status updated to: Closed (was: Open)

4 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/3070

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata