Bug 1320455 (rhel7-openssl-no-ssl2) - Remove SSL 2.0 support to avoid supporting it for lifetime of RHEL-7
Summary: Remove SSL 2.0 support to avoid supporting it for lifetime of RHEL-7
Keywords:
Status: CLOSED ERRATA
Alias: rhel7-openssl-no-ssl2
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openssl
Version: 7.2
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: Stefan Dordevic
Mirek Jahoda
URL:
Whiteboard:
Depends On:
Blocks: 1335929 1377248
TreeView+ depends on / blocked
 
Reported: 2016-03-23 09:31 UTC by Tomas Mraz
Modified: 2017-08-01 18:16 UTC (History)
5 users (show)

Fixed In Version: openssl-1.0.2k-3.el7
Doc Type: Deprecated Functionality
Doc Text:
The SSL 2.0 support is completely removed from OpenSSL The SSL 2.0 protocol is severally broken and insecure, it was deprecated many years ago and it is not used anymore. Its support was already disabled by default. However to avoid inadvertent reenablement of the insecure protocol its support was removed completely. The OpenSSL library API calls that implement the protocol will permanently return error.
Clone Of:
Environment:
Last Closed: 2017-08-01 18:16:10 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
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 Tomas Mraz 2016-03-23 09:31:27 UTC 
We should completely remove the support for SSL 2.0 except for receiving SSLv2 client hellos on the server.

The support will not be compiled into the library. To avoid ABI break the SSL2 specific public functions will be kept but they will return an error.
Comment 5 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.

https://access.redhat.com/errata/RHBA-2017:1929
Note You need to log in before you can comment on or make changes to this bug.