This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2229209 - entries "epo" and "map" in hostname_map section of default_mappings change the "sosreport" file name
Summary: entries "epo" and "map" in hostname_map section of default_mappings change th...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sos
Version: 8.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Pavel Moravec
QA Contact: Supportability QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-04 16:02 UTC by Carlos Santos
Modified: 2023-09-06 13:53 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-06 13:53:40 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-2399 0 None Migrated None 2023-09-06 13:53:34 UTC
Red Hat Issue Tracker RHELPLAN-164583 0 None None None 2023-08-04 16:03:03 UTC

Description Carlos Santos 2023-08-04 16:02:29 UTC 
Description of problem:

When the hostname_map section in /etc/sos/cleaner/default_mapping contains
entries like these,



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


How reproducible:

Always

Steps to Reproduce:

1. Ensure that sos report will find hosts with name "epo" and "map"

   # echo 192.168.122.1 epo.map.example.com epo map >> /etc/hosts

2. Remove the existing default mapping

   # rm -f /etc/sos/cleaner/default_mapping

3. Generate the report

   # sos report --batch --case-id 00000000 --clean

Actual results:

[...]
sosreport-<hostname>-00000000-2023-08-04-zddhrim :   Beginning obfuscation...
sosreport-<hostname>-00000000-2023-08-04-zddhrim :   Obfuscation completed [removed 920 unprocessable files]

Successfully obfuscated 1 report(s)

Creating compressed archive...

A mapping of obfuscated elements is available at
	/var/tmp/sosrhost1rt-host140-00000000-2023-08-04-zddhrim-private_map

Your sosreport has been generated and saved in:
	/var/tmp/sosrhost141rt-host14140-00000000-2023-08-04-zddhrim-obfuscated.tar.xz

 Size	6.36MiB
 Owner	root
 sha256	3c9e8df05545a6d57c058e03ea0d474dbdf8720b6d59a8493d3985b309cf1b75

Please send this file to your support representative.

Expected results:

Your sosreport has been generated and saved in:
	/var/tmp/sosreport-host14140-00000000-2023-08-04-zddhrim-obfuscated.tar.xz

Additional info:
Comment 1 Pavel Moravec 2023-08-05 21:08:30 UTC 
This is tricky.

Sos takes /etc/hosts for hostname mapping. So whatever string is there, it treats it as a sensitive information to obfuscate. So for e.g. "rep" in /etc/hosts, "sosreport" string is obfuscated - including tarball filename (as it usually contains host's shortname).

How to behave better? Obfuscate not (sub)strings blindly, but for each string STR to camouflage, find just strings matching [^|\W]STR[$|\W] regular expression? (i.e. start of line or non-alphanumeric character before the STR, and end of line or non-alphanumeric character after the STR)?

What about *not* obfuscating "rep01", then? Is it ok? (I feel so..)


sos cleaner has a few parsers/mappers, one for hostnames+domainnames, one for IPv4, one for IPv6, one for MAC addresses, usernames and keywords (provided by user via a config). I guess this feature "dont obfuscate substrings, just strings" should be applied only to:
- hostnames+domainnames
- usernames
- keywords

As only those are alphanumeric words.

Is that improvement sound?
Comment 2 Carlos Santos 2023-08-07 12:26:34 UTC 
(In reply to Pavel Moravec from comment #1)

> sos cleaner has a few parsers/mappers, one for hostnames+domainnames, one
> for IPv4, one for IPv6, one for MAC addresses, usernames and keywords
> (provided by user via a config). I guess this feature "dont obfuscate
> substrings, just strings" should be applied only to:
> - hostnames+domainnames
> - usernames
> - keywords
> 
> As only those are alphanumeric words.
> 
> Is that improvement sound?

I will ask the customer in the associated support case if that's a satisfying
approach.
Comment 3 Carlos Santos 2023-08-08 16:34:51 UTC 
(In reply to Pavel Moravec from comment #1)

> sos cleaner has a few parsers/mappers, one for hostnames+domainnames, one
> for IPv4, one for IPv6, one for MAC addresses, usernames and keywords
> (provided by user via a config). I guess this feature "dont obfuscate
> substrings, just strings" should be applied only to:
> - hostnames+domainnames
> - usernames
> - keywords
> 
> As only those are alphanumeric words.
> 
> Is that improvement sound?

According to the customer, that seems fine, but mostly concerning are the
single and double chars masking. It might lead to unknown issues, like
decreased time of cleaning, with wrong masking of insensitive chars.

---> "e": "host22",
Comment 4 RHEL Program Management 2023-09-06 13:50:53 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 5 RHEL Program Management 2023-09-06 13:53:40 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.
Note You need to log in before you can comment on or make changes to this bug.