Bug 1608425

Summary: rhnlib allows creation of SSLv2 and SSLv3 connections during protocol negotiation
Product: Red Hat Enterprise Linux 7 Reporter: Tomáš Kašpárek <tkasparek>
Component: rhnlibAssignee: Tomáš Kašpárek <tkasparek>
Status: CLOSED ERRATA QA Contact: Jan Hutař <jhutar>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.6CC: jhutar, mmraka, smoroney, tkasparek, tlestach
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhnlib-2.5.65-8.el7 Doc Type: Enhancement
Doc Text:
Feature: Disallowing older SSL versions in order to increase application security. Reason: Increasing application security. Result: All communication between Satellite 5 and its clients is now TLS only as SSLv2 and SSLv3 has been forbidden during secure connection negotiation.
Story Points: ---
Clone Of:
: 1643415 (view as bug list) Environment:
Last Closed: 2018-10-30 11:49:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1607917, 1643415    

Description Tomáš Kašpárek 2018-07-25 13:56:10 UTC
Description of problem:
rhnlib allows creation of SSLv2 and SSLv3 connections during protocol negotiation as options OP_NO_SSLv2 and OP_NO_SSLv3 are not set.
Although tcdpdump shows that TLSv1.2 is used, we should explicitly forbid usage of SSLv2 and SSLv3.

Version-Release number of selected component (if applicable):
rhnlib-2.5.65-7-el7

Comment 2 Tomáš Kašpárek 2018-07-26 07:58:27 UTC
spacewalk.git(master): 670e3205184a8de2fce82981306b04a52c146648

Comment 12 errata-xmlrpc 2018-10-30 11:49:11 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-2018:3318