Bug 1331325

Summary: [PATCH] Disable sslv3 in nagios-plugins
Product: [Fedora] Fedora Reporter: Codarren Velvindron <codarren>
Component: nagios-pluginsAssignee: Stephen John Smoogen <smooge>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 25CC: kmf, mhayden, ondrejj, smooge, swilkerson
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-20 21:40:44 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:
Description Flags
Disable sslv3
nagios-plugins spec diff none

Description Codarren Velvindron 2016-04-28 10:01:03 UTC
Created attachment 1151792 [details]
Disable sslv3

Description of problem:https://www.rfc-editor.org/rfc/rfc7568.txt
According to rfc7568, sslv3 is no longer considered secure. This patch disables sslv3 if the system's openssl is compiled without it.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 1 Codarren Velvindron 2016-04-28 10:02:48 UTC
Created attachment 1151794 [details]
nagios-plugins spec diff

Comment 2 Jan Kurik 2016-07-26 04:50:07 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 3 Fedora Admin XMLRPC Client 2017-01-17 19:38:50 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Stephen John Smoogen 2017-01-18 00:25:33 UTC
This patch looks to have been fixed and closed in upstream 2.1.4 with the patch attached. An updated package will be built into Fedora 24 and 25 this week.

Comment 5 Stephen John Smoogen 2017-01-20 21:40:44 UTC
This bug is considered closed in 2.1.4