Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
This bug was initially created as a copy of Bug #2043233
I am copying this bug because:
we need to have 8.8 and 9.2 in par
Description of problem:
After installing sos version 4.0-12.el8.4 on an IdM server, I run "sos report --clean" or "sos --clean" and I get a cleaned sos report in a tar file. When I untar the cleaned report, I find sensitive information left in the file content, directory names, and file names.
Version-Release number of selected component (if applicable):
4.0-12.el8.4
How reproducible:
Reproducible every time for an IdM server on RHEL 8.4
Steps to Reproduce (example.com is not the real domain since the real one is sensitive)
yum -y install sos
sos clean --domains example.com,ca.example.com,nj.example.com --keywords example.com, ca.example.com, nj.example.com sosreport.tar
Number 2 generates a cleaned sosreport.tar.xz and a sosreport_private_map
Untarred the sosreport.tar.xz
cd into the sosreport directory
grep -ir example.com . # EXAMPLE-COM was not obfuscated
grep -ir 'dc=example,dc=com' . # dc=example,dc=com was not obfuscated
grep -Er '192.168.' # 192.168.x.in-addr.arpa >8. records returned where x is a number after '192.168.'
find . -type d > directories.txt
grep -ir example.com directories.txt #EXAMPLE-COM was not obfuscated in the directories
grep -ir 15.3.168.192 directories.txt #Returns 15.3.168.192.in-addr.arpa directories
find . type f > filesnames.txt
grep -ir example.com filenames.txt # EXAMPLE-COM was not obfuscated in the filenames
Actual results:
domains and ip addresses are not getting obfuscated.
Expected results:
all sensitive data should be obfuscated
Additional info:
None