Bug 1162788

Summary: remove password leak from ovirt-engine setup answer file
Product: Red Hat Enterprise Linux 7 Reporter: Dave Sullivan <dsulliva>
Component: sosAssignee: Pavel Moravec <pmoravec>
Status: CLOSED ERRATA QA Contact: David Kutálek <dkutalek>
Severity: high Docs Contact: Jiri Herrmann <jherrman>
Priority: high    
Version: 7.2CC: agk, dkutalek, ecohen, iheim, isenfeld, jherrman, jkurik, lsurette, pmoravec, pstehlik, rbalakri, Rhev-m-bugs, sbonazzo, yeylon
Target Milestone: rcKeywords: Patch, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sos-3.2-17.el7 Doc Type: Bug Fix
Doc Text:
Prior to this update, the ovirt plug-in for the sos utility did not properly obfuscate the passwords in the ovirt-engine setup answer file, and the passwords were thus collected in plain text format. With this update, the passwords are now obfuscated as intended, and no longer collected.
Story Points: ---
Clone Of: 1162781
: 1214024 (view as bug list) Environment:
Last Closed: 2015-11-19 12:14:16 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:
Bug Depends On: 1162781    
Bug Blocks: 1133060, 1205796, 1214024    
Attachments:
Description Flags
fix for upstream sos master none

Description Dave Sullivan 2014-11-11 17:11:39 UTC
+++ This bug was initially created as a clone of Bug #1162781 +++

Description of problem:


Initial passwords leaked here: <rhevm-host-sosreport-tarball>/var/lib/ovirt-engine/setup/answers/YYYYMMDDHHMMSS-setup.conf

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

3.X

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

****** out passwords


Additional info:

Comment 2 Sandro Bonazzola 2014-11-14 13:58:31 UTC
Created attachment 957596 [details]
fix for upstream sos master

Comment 9 errata-xmlrpc 2015-11-19 12:14:16 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://rhn.redhat.com/errata/RHBA-2015-2118.html