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.

Bug 1963917

Summary: [RFE] Data redaction for branch_info file
Product: Red Hat Enterprise Linux 8 Reporter: Olimp Bockowski <obockows>
Component: insights-clientAssignee: Christian Marineau <cmarinea>
Status: CLOSED MIGRATED QA Contact: Red Hat subscription-manager QE Team <rhsm-qe>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.4CC: bfahr, cmarinea, gchamoul, gmccullo, kdixon, link, pakotvan
Target Milestone: betaKeywords: FutureFeature, MigratedToJIRA, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-07 13:08:26 UTC Type: Story
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Olimp Bockowski 2021-05-24 12:05:51 UTC
Description of problem:
One can obfuscate hostname and also configure properly file-content-redaction.yaml to filter out a domain but still the branch_info includes Satellite's hostname/FQDN/domain part

Version-Release number of selected component (if applicable):
<= insights-client-3.1.3-2

How reproducible:
always

Steps to Reproduce:
1. edit /etc/insights-client/file-content-redaction.yaml
2. put for example

patterns:
  regex:
    - "obockows"


3. run: insights-client --no-upload
4. unpack soscleaner*
5. check branch_info file:

[root@rhel8 soscleaner-2354462507999389]# cat ./branch_info  | grep -o -P 'obockows.*?' 
obockows
obockows
obockows


Actual results:
There is still the exact string that is supposed to be filtered out

Expected results:
Even branch_info falls under limitations we would like to have

Additional info:

Comment 3 Link Dupont 2022-03-15 16:41:39 UTC
Will this cause any problems with host identification if the hostname is removed or obfuscated from within the branch_info file?

Comment 4 Link Dupont 2022-03-28 15:12:28 UTC
Olimp, I looked into this more, and our current obfuscation behavior only obfuscates files under the `./data` directory of an archive. The branch_info file exists at the root of the archive, so it is not included when obfuscating file content. Before we proceed with changing the obfuscation behavior to include branch_info, we'll need to make sure that the data in that file isn't relied upon by some service or services to identify a host.

Comment 7 RHEL Program Management 2023-09-07 13:05:55 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 8 RHEL Program Management 2023-09-07 13:08:26 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.