Bug 1513886 - [downstream clone - 4.1.8] [RFE] Enable TLSv12 support by default
Summary: [downstream clone - 4.1.8] [RFE] Enable TLSv12 support by default
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 4.1.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.1.8
: ---
Assignee: Piotr Kliczewski
QA Contact: Jiri Belka
URL:
Whiteboard:
Depends On: 1511962
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-16 08:41 UTC by rhev-integ
Modified: 2019-04-28 13:08 UTC (History)
9 users (show)

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.
Clone Of: 1511962
Environment:
Last Closed: 2017-12-12 09:24:07 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:3428 0 normal SHIPPED_LIVE VDSM bug fix and enhancement update 4.1.8 2017-12-12 14:16:56 UTC
oVirt gerrit 84064 0 ovirt-4.1 MERGED config: enable tlsv12 by default 2021-02-05 12:09:14 UTC

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
Note You need to log in before you can comment on or make changes to this bug.