--domainsDOMAINS
Provide a comma-delimited list of domain names to obfuscate, in addition to those matching the
hostname of the system that created the sos report. Subdomains that match a domain given via this
option will also be obfuscated.
For example, if --domainsredhat.com is specified, then 'redhat.com' will be obfuscated, as will
'www.redhat.com' and subdomains such as 'foo.redhat.com'.
--disable-parsersPARSERS
Provide a comma-delimited list of parsers to disable when cleaning an archive. By default all
parsers are enabled.
Note that using this option is very likely to leave sensitive information in place in the target
archive, so only use this option when absolutely necessary or you have complete trust in the
party/parties that may handle the generated report.
Valid values for this option are currently: hostname, ip, ipv6, mac, keyword, and username.
--skip-cleaning-files,--skip-masking-filesFILES
Provide a comma-delimited list of files inside an archive, that cleaner should skip in cleaning.
Globs like asterisk are supported, so sos_commands/host/hostname* will match all three usual
filenames in that directory (hostname, hostnamectl_status and hostname_-f).
Use this option with caution, only when being certain the given files do not contain any sensitive
information.
--keywordsKEYWORDS
Provide a comma-delimited list of keywords to scrub in addition to the default parsers.
Keywords provided by this option will be obfuscated as "obfuscatedwordX" where X is an integer
based on the keyword's index in the parser. Note that keywords will be replaced as both standalone
words and in substring matches.
--keyword-fileFILE
Provide a file that contains a list of keywords that should be obfuscated. Each word must be
specified on a newline within the file.
--map-fileFILE
Provide a location to a valid mapping file to use as a reference for existing obfuscation pairs.
If one is found, the contents are loaded before parsing is started. This allows consistency
between runs of this command for obfuscated pairs. By default, sos will write the generated
private map file to /etc/sos/cleaner/default_mapping so that consistency is maintained by default.
Users may use this option to reference a map file from a different run (perhaps one that was done
on another system).
Default: /etc/sos/cleaner/default_mapping
--jobsJOBS
The number of concurrent archives to process, if more than one. If this utility is called by soscollect then the value of the jobs option for that utility will be used here.
Default: 4
--no-update
Do not write the mapping file contents to /etc/sos/cleaner/default_mapping
--keep-binary-files
Keep unprocessable binary files in the archive, rather than removing them.
Note that binary files cannot be obfuscated, and thus keeping them in the archive may result in
otherwise sensitive information being included in the final archive. Users should review any
archive that keeps binary files in place before sending to a third party.
Default: False (remove encountered binary files)
--archive-typeTYPE
Specify the type of archive that TARGET was generated as. When sos inspects a TARGET archive, it
tries to identify what type of archive it is. For example, it may be a report generated by sosreport, or a collection of those reports generated by soscollect, which require separate
approaches.
This option may be useful if a given TARGET archive is known to be of a specific type, but due to
unknown reasons or some malformed/missing information in the archive directly, that is not
properly identified by sos.
The following are accepted values for this option:
auto Automatically detect the archive type
report An archive generated by sosreportcollect An archive generated by soscollectinsights An archive generated by the insights-client package
The following may also be used, however note that these do not attempt to pre-load any information
from the archives into the parsers. This means that, among other limitations, items like host and
domain names may not be obfuscated unless an obfuscated mapping already exists on the system from
a previous execution.
data-dir A plain directory on the filesystem.
tarball A generic tar archive not associated with any known tool