Bug 1412550 - Fix certificate validation for engine <-> VDSM encrypted connection when IPv6 is configured
Summary: Fix certificate validation for engine <-> VDSM encrypted connection when IPv6...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Bindings-API
Version: 4.20.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.1.1
: 4.19.6
Assignee: Piotr Kliczewski
QA Contact: Jiri Belka
URL:
Whiteboard:
Depends On:
Blocks: RHV_TLS_1_2_SUPPORT
TreeView+ depends on / blocked
 
Reported: 2017-01-12 09:35 UTC by Martin Perina
Modified: 2017-04-21 09:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-21 09:32:39 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: planning_ack+
mperina: devel_ack+
pstehlik: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 70083 0 master MERGED ssl: trust ipv6 localhost addresses 2017-01-30 10:18:53 UTC
oVirt gerrit 72199 0 ovirt-4.1 MERGED sslutils: _compare_names: fix arg names and add tests 2017-02-14 10:15:59 UTC
oVirt gerrit 72200 0 ovirt-4.1 MERGED ssl: trust ipv6 localhost addresses 2017-02-14 11:23:24 UTC

Description Martin Perina 2017-01-12 09:35:21 UTC 
Description of problem:

When we compare client name during establishing a secured connection between engine and VDSM, we don't properly handle IPv6 addresses.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Martin Perina 2017-01-18 08:58:34 UTC 
Missed RC build, moving to 4.1.1
Comment 2 Jiri Belka 2017-03-06 15:41:19 UTC 
ok, vdsm-4.19.7-1.el7ev.x86_64

communication via ipv6 on the host internally

# for i in 0 localhost `hostname`; do vdsClient -s $i getVdsCaps 2>&1 | grep software_version ; done
        software_version = '4.19'
        software_version = '4.19'
        software_version = '4.19'
Note You need to log in before you can comment on or make changes to this bug.