Bug 1061639

Summary:	[Security] vdsm libvirt authentication is static and public
Product:	[Retired] oVirt	Reporter:	Sven Kieske <s.kieske>
Component:	vdsm	Assignee:	Dan Kenigsberg <danken>
Status:	CLOSED NOTABUG	QA Contact:	Aharon Canan <acanan>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.4	CC:	abaron, acathrow, bazulay, dougsland, gklein, iheim, mgoldboi, pdwyer, yeylon
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-05 12:18:28 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:

Description Sven Kieske 2014-02-05 09:48:54 UTC

Description of problem:
The password and user for the authentication towards libvirt are static, the
user is vdsm@ovirt and the password is in gerrit and never gets changed after
installation:

http://gerrit.ovirt.org/gitweb?p=vdsm.git;a=blob;f=vdsm/libvirt_password;h=09e60bce9bc401bb8943154f7cb9cb08bd0f49da;hb=refs/heads/master

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

latest master and also present in 3.3.2 production release.

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:

everyone with access to the sourcecode (so: everyone)
can interact with libvirt, once access to the hypervisor machine is gained

Expected results:

generate a random password, use diffie-hellman, anything secure, but no static
password for the whole userbase of ovirt.
Additional info:

Comment 1 Dan Kenigsberg 2014-02-05 12:18:28 UTC

The "password" that Vdsm uses to communicate with libvirt over the host-local vdsm-owned unix domain socket is NOT a security measure. It is an obfuscation of the read/write libvirt interface, designed to deter local administrators from changing libvirt directly.

Cf. bug 570526 about the sad history of this request.

Comment 2 Dan Kenigsberg 2016-03-20 13:51:36 UTC

*** Bug 1309769 has been marked as a duplicate of this bug. ***