-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
rhel-10.1, rhel-9.7
-
None
-
Yes
-
Moderate
-
rhel-sst-cee-supportability
-
None
-
False
-
False
-
-
None
-
None
-
Pass
-
RegressionOnly
-
Unspecified
-
Unspecified
-
Unspecified
-
-
All
-
None
What were you trying to do that didn't work?
Running sos report --clean and hoping my hostname or FQDN wont be in obfuscated archive.
What is the impact of this issue to you?
Risk of leaking sensitive data from customers to us.
Please provide the package NVR for which the bug is seen:
sos-4.10.2-1
How reproducible is this bug?:
100%
Steps to reproduce
- sos report --batch --build --clean
- record generated archive filename and private_map file, and adjust below commands accordingly
- grep $(hostname -f) /var/tmp/sosreport-host0-2026-01-30-entfbyg-private_map # to ensure cleaner detected my hostname for cleanup
- grep $(hostname -f) /var/tmp/sosreport-host0-2026-01-30-entfbyg -r # to check if my FQDN hostname is completely obfuscated or not
Expected results
3. shows a line like
"pmoravec-rhel9.some.domain.redhat.com": "host0.obfuscateddomain1.com",
4. shows nothing (all cleaned)
Actual results
4. shows:
/var/tmp/sosreport-host0-2026-01-30-entfbyg/etc/pki/consumer/cert.pem.text: DirName:/O=RedHat/CN=18b941d4-9fd7-405a-a9af-9605b8238b91, DirName:/CN=pmoravec-rhel9.some.domain.redhat.com
as the system is registered to a RHSM server (mine to a Satellite, imho registering to rhsm.redhat.com will be the same), and its entitlement cert (converted to text) keeps my FQDN
- links to
-
RHBA-2026:158184
sos bug fix and enhancement update