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.

Description of problem:
The subscription_manager plugin collects the "/var/lib/rhsm/" path, but on that path a copy of a repository file may exist, which in turn may contain e.g. proxy usernames and passwords.

Version-Release number of selected component (if applicable):
sos-4.3-5.el8.noarch (but upstream is affected too)

How reproducible:
Always

Steps to Reproduce:
1. Edit /var/lib/rhsm/repo_server_val/redhat.repo and add "proxy", "proxy_username", and "proxy_password" to any of the repositories:

proxy=http://proxy.example.com:3128/
proxy_username=foobar
proxy_password=hackme

2. Run the sos report subscription_manager plugin:

    # sos report -o subscription_manager


Actual results:
Collected /var/lib/rhsm/repo_server_val/redhat.repo still contains the password.

Expected results:
The password is scrubbed off.

Additional info:
https://github.com/sosreport/sos/issues/3163
https://github.com/sosreport/sos/pull/3164

Switched to Tested based on manual test results. Stepan feel free to test the package too. Thanks for helping us!

old:
===

[root@ci-vm-10-0-138-118 repo_server_val]# sos report -o subscription_manager

sosreport (version 4.5.1)

...

[root@ci-vm-10-0-138-118 repo_server_val]# cat redhat.repo 
proxy=http://proxy.example.com:3128/
proxy_username=foobar
proxy_password=hackme


new:
===
[root@ci-vm-10-0-136-145 ~]# sos report -o subscription_manager

sosreport (version 4.5.3)

...

[root@ci-vm-10-0-136-145 tmp]# cat sosreport-ci-vm-10-0-136-145-2023-05-17-smumlcm/var/lib/rhsm/repo_server_val/redhat.repo 
proxy=http://proxy.example.com:3128/
proxy_username=foobar
proxy_password=********

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 (sos bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2023:3414