Bug 1240666

Summary: openstack_neutron does not obscure passwords, secrets etc.
Product: Red Hat Enterprise Linux 7 Reporter: Lee Yarwood <lyarwood>
Component: sosAssignee: Pavel Moravec <pmoravec>
Status: CLOSED ERRATA QA Contact: David Kutálek <dkutalek>
Severity: high Docs Contact:
Priority: high    
Version: 7.1CC: agk, bmr, chhudson, gavin, isenfeld, jherrman, plambri, sbradley
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: sos-3.2-25.el7 Doc Type: Bug Fix
Doc Text:
Previously, various OpenStack plug-ins for the sosreport utility were incorrectly collecting passwords in plain text. As a consequence, the compressed file created after using sosreport could contain human-readable passwords. This update adds obfuscation of all passwords to sosreport OpenStack plug-ins, and the affected passwords in the sosreport tarball are no longer human-readable.
Story Points: ---
Clone Of:
: 1240667 1242009 1242871 (view as bug list) Environment:
Last Closed: 2015-11-19 12:18:51 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:    
Bug Blocks: 1240667, 1242009, 1242871    

Description Lee Yarwood 2015-07-07 13:05:44 UTC
Description of problem:
openstack_neutron does not obscure passwords, secrets etc.

# grep ^rabbit_password etc/neutron/neutron.conf 
rabbit_password = d873fe7e27346b7191887fd890504787b618f227

Version-Release number of selected component (if applicable):
sos-3.2-15.el7_1.1.noarch

How reproducible:
Always

Steps to Reproduce:
1. # sosreport -o openstack_neutron

Actual results:
/etc/neutron config files collected with passwords and secrects still present.

Expected results:
/etc/neutron config files collected with passwords and secrects obscured.

Additional info:

Comment 10 errata-xmlrpc 2015-11-19 12:18:51 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