Bug 1513886

Summary: [downstream clone - 4.1.8] [RFE] Enable TLSv12 support by default
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: vdsmAssignee: Piotr Kliczewski <pkliczew>
Status: CLOSED ERRATA QA Contact: Jiri Belka <jbelka>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.5CC: bazulay, bgraveno, lsurette, lveyde, mgoldboi, mperina, srevivo, ycui, ykaul
Target Milestone: ovirt-4.1.8Keywords: FutureFeature, Improvement, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: vdsm v4.19.38 Doc Type: Release Note
Doc Text:
This update ensures that TLSv12 support is enabled by default and no manual configuration is required.
Story Points: ---
Clone Of: 1511962 Environment:
Last Closed: 2017-12-12 09:24:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1511962    
Bug Blocks:    

Description rhev-integ 2017-11-16 08:41:51 UTC
+++ This bug is a downstream clone. The original bug is: +++
+++   bug 1511962 +++
======================================================================

Description of problem:

We have backported TLSv12 support into RHV 4.1.5 (BZ1412552), but it was turned off by default and enabled TLSv12 required manual configuration. We want to enable TLSv12 by default to make it aligned with RHV 4.2

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

(Originally by Martin Perina)

Comment 1 Jiri Belka 2017-11-30 13:09:13 UTC
ok, vdsm-4.19.40-1.el7ev.x86_64 ovirt-engine-4.1.8.1-0.1.el7.noarch

Comment 5 errata-xmlrpc 2017-12-12 09:24:07 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/RHEA-2017:3428