Bug 1335940 - Disable/remove export ciphersuites in OpenSSL
Summary: Disable/remove export ciphersuites in OpenSSL
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openssl
Version: 7.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: Stefan Dordevic
Mirek Jahoda
Depends On:
Blocks: 1377248 1335929
TreeView+ depends on / blocked
Reported: 2016-05-13 15:09 UTC by Nikos Mavrogiannopoulos
Modified: 2017-08-01 18:16 UTC (History)
3 users (show)

Fixed In Version: openssl-1.0.2k-1.el7
Doc Type: Deprecated Functionality
Doc Text:
The EXPORT cipher suites in *OpenSSL* are deprecated This change removes support for the EXPORT cipher suites in the *OpenSSL* toolkit. Disabling the weak cipher suites prevents attacks such as the FREAK attack. The EXPORT cipher suites are not required in any *TLS* protocol configuration.
Clone Of:
Last Closed: 2017-08-01 18:16:10 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1929 0 normal SHIPPED_LIVE openssl bug fix and enhancement update 2017-08-01 18:08:01 UTC

Description Nikos Mavrogiannopoulos 2016-05-13 15:09:47 UTC
RHEL includes several cryptographic components who's security doesn't remain constant over time. Algorithms such as (cryptographic) hashing and encryption typically have a lifetime after which they are considered either too risky to use or plain insecure. That would mean we need to phase out such algorithms from the default settings, or completely disable if they could cause irreparable issue. 

This bug is about disabling by default and removing the ability to negotiate the marked as EXPORT ciphersuites. It should not be possible by applications to inadvertently enable them.

Comment 6 errata-xmlrpc 2017-08-01 18:16:10 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.


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