1sechecker(1) General Commands Manual sechecker(1)
2
6 sechecker - SELinux policy checking tool
7
9 sechecker [OPTIONS] -p profile [POLICY ...]
10 sechecker [OPTIONS] -m module [POLICY ...]
11 sechecker [OPTIONS] -p profile -m module [POLICY ...]
12
14 sechecker allows the user to perform predefined modular checks on a
15 SELinux policy. Profiles exist to group modules together and allow
16 modification of module settings (see below).
17
19 sechecker supports loading a SELinux policy in one of four formats.
20 source A single text file containing policy source for versions 12
22 through 21. This file is usually named policy.conf.
23 binary A single file containing a monolithic kernel binary policy for
25 versions 15 through 21. This file is usually named by version -
26 for example, policy.20.
27 modular
29 A list of policy packages each containing a loadable policy mod‐
30 ule. The first module listed must be a base module.
31 policy list
33 A single text file containing all the information needed to load
34 a policy, usually exported by SETools graphical utilities.
35 If no policy file is provided, sechecker will search for the system
37 default policy: checking first for a source policy, next for a binary
38 policy matching the running kernel's preferred version, and finally for
39 the highest version that can be found. If no policy can be found,
40 sechecker will print an error message and exit.
41
43 -p PROFILE, --profile=PROFILE
44 Load module settings from a module profile. The settings in the
45 profile will override the default settings for all specified
46 modules. If specified without -m, run all modules in the pro‐
47 file. PROFILE may either be the name of a known profile (see
48 --list) or the path to a user created profile. see PROFILE
49 OPTIONS below for more information about creating profiles.
50 -m MODULE, --module=MODULE
52 Run only the module named MODULE (see --list).
53 --min-sev=SEVERITY
55 Report only results with the minimum severity of SEVERITY.
56 SEVERITY must have one of the following values:
57 low The module's results indicate a flaw in the policy that
59 does not affect the manner in which the policy is
60 enforced, but is considered to be improper.
61 med The module's results indicate a flaw in the policy that
63 changes the manner in which the policy is enforced; how‐
64 ever, it does not present an identifiable security risk.
65 high The module's results indicate a flaw in the policy that
67 presents an identifiable security risk.
68 --fcfile=FILE
70 Use FILE for the file_contexts file instead of the system
71 default. This flag is only applicable if sechecker was config‐
72 ured with the --enable-sefs flag.
73 -l, --list
75 Print a list of the name and a brief description of all known
76 profiles and modules and exit.
77 -h[MODULE], --help[=MODULE]
79 Print general help information and exit. If MODULE is provided,
80 print help information for the module named MODULE and exit.
81 -V, --version
83 Print version information and exit.
84 REPORT GENERATION OPTIONS
86 Only one of the following may be provided to specify the length of the
87 report for all modules. If provided, this option overrides both pro‐
88 file and module default output settings.
89 -q, --quiet
91 suppress output
92 -s, --short
94 print short output
95 -v, --verbose
97 print verbose output
98
100 Profiles are used to group modules together, to specify the output for‐
101 mat for each module in the report, and to provide the ability to over‐
102 ride the modules' default options. Each profile is a well-formed XML
103 document, as specified by the DTD installed with sechecker. An example
104 profile follows:
105 <sechecker version="1.1">
107 <profile>
108 <module name="find_domains">
109 <output value="quiet"/>
110 <option name="domain_attribute">
111 <item value="domain"/>
112 <item value="user_domain"/>
113 ...
114 </option>
115 </module>
116 ...
117 </profile>
118 </sechecker>
119 The example profile specifies the output property for the find_domains
121 module. The example profile also overrides the default value for the
122 "domain_attribute" option in the find_domains module.
123 PROFILE OUTPUT OPTIONS
125 The valid output values for each module are specified below:
126 verbose
128 Print each result in the report with accompanying proof(s).
129 short Print a list of results with no accompanying proof.
131 none Do not print output from this module in the report; however,
133 module errors will still be printed.
134 quiet Do not print output from this module in the report and do not
136 print errors. This is useful for utility modules for which the
137 calling module handles any errors.
138 PROFILE MODULE OPTIONS
140 Several modules provide one or more options that can be set from a pro‐
141 file. Each option has one or more items. To check what options are
142 available for a module use --help=MODULE, where MODULE is the name of
143 the module as printed by --list.
144
146 This manual page was written by Jeremy A. Mowery <jmowery@tresys.com>.
147
149 Copyright(C) 2005-2007 Tresys Technology, LLC
150
152 Please report bugs via an email to setools-bugs@tresys.com.
153
155 apol(1)
156 sechecker(1)