1callweaver_selinux(8) SELinux Policy callweaver callweaver_selinux(8)
2
3
4
6 callweaver_selinux - Security Enhanced Linux Policy for the callweaver
7 processes
8
10 Security-Enhanced Linux secures the callweaver processes via flexible
11 mandatory access control.
12
13 The callweaver processes execute with the callweaver_t SELinux type.
14 You can check if you have these processes running by executing the ps
15 command with the -Z qualifier.
16
17 For example:
18
19 ps -eZ | grep callweaver_t
20
21
22
24 The callweaver_t SELinux type can be entered via the callweaver_exec_t
25 file type.
26
27 The default entrypoint paths for the callweaver_t domain are the fol‐
28 lowing:
29
30 /usr/sbin/callweaver
31
33 SELinux defines process types (domains) for each process running on the
34 system
35
36 You can see the context of a process using the -Z option to ps
37
38 Policy governs the access confined processes have to files. SELinux
39 callweaver policy is very flexible allowing users to setup their call‐
40 weaver processes in as secure a method as possible.
41
42 The following process types are defined for callweaver:
43
44 callweaver_t
45
46 Note: semanage permissive -a callweaver_t can be used to make the
47 process type callweaver_t permissive. SELinux does not deny access to
48 permissive process types, but the AVC (SELinux denials) messages are
49 still generated.
50
51
53 SELinux policy is customizable based on least access required. call‐
54 weaver policy is extremely flexible and has several booleans that allow
55 you to manipulate the policy and run callweaver with the tightest
56 access possible.
57
58
59
60 If you want to allow all domains to execute in fips_mode, you must turn
61 on the fips_mode boolean. Enabled by default.
62
63 setsebool -P fips_mode 1
64
65
66
68 The SELinux process type callweaver_t can manage files labeled with the
69 following file types. The paths listed are the default paths for these
70 file types. Note the processes UID still need to have DAC permissions.
71
72 callweaver_spool_t
73
74 /var/spool/callweaver(/.*)?
75
76 callweaver_var_lib_t
77
78 /var/lib/callweaver(/.*)?
79
80 callweaver_var_run_t
81
82 /var/run/callweaver(/.*)?
83
84 cluster_conf_t
85
86 /etc/cluster(/.*)?
87
88 cluster_var_lib_t
89
90 /var/lib/pcsd(/.*)?
91 /var/lib/cluster(/.*)?
92 /var/lib/openais(/.*)?
93 /var/lib/pengine(/.*)?
94 /var/lib/corosync(/.*)?
95 /usr/lib/heartbeat(/.*)?
96 /var/lib/heartbeat(/.*)?
97 /var/lib/pacemaker(/.*)?
98
99 cluster_var_run_t
100
101 /var/run/crm(/.*)?
102 /var/run/cman_.*
103 /var/run/rsctmp(/.*)?
104 /var/run/aisexec.*
105 /var/run/heartbeat(/.*)?
106 /var/run/corosync-qnetd(/.*)?
107 /var/run/corosync-qdevice(/.*)?
108 /var/run/corosync.pid
109 /var/run/cpglockd.pid
110 /var/run/rgmanager.pid
111 /var/run/cluster/rgmanager.sk
112
113 root_t
114
115 /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
116 /
117 /initrd
118
119
121 SELinux requires files to have an extended attribute to define the file
122 type.
123
124 You can see the context of a file using the -Z option to ls
125
126 Policy governs the access confined processes have to these files.
127 SELinux callweaver policy is very flexible allowing users to setup
128 their callweaver processes in as secure a method as possible.
129
130 STANDARD FILE CONTEXT
131
132 SELinux defines the file context types for the callweaver, if you
133 wanted to store files with these types in a diffent paths, you need to
134 execute the semanage command to sepecify alternate labeling and then
135 use restorecon to put the labels on disk.
136
137 semanage fcontext -a -t callweaver_spool_t '/srv/mycallweaver_con‐
138 tent(/.*)?'
139 restorecon -R -v /srv/mycallweaver_content
140
141 Note: SELinux often uses regular expressions to specify labels that
142 match multiple files.
143
144 The following file types are defined for callweaver:
145
146
147
148 callweaver_exec_t
149
150 - Set files with the callweaver_exec_t type, if you want to transition
151 an executable to the callweaver_t domain.
152
153
154
155 callweaver_initrc_exec_t
156
157 - Set files with the callweaver_initrc_exec_t type, if you want to
158 transition an executable to the callweaver_initrc_t domain.
159
160
161
162 callweaver_log_t
163
164 - Set files with the callweaver_log_t type, if you want to treat the
165 data as callweaver log data, usually stored under the /var/log direc‐
166 tory.
167
168
169
170 callweaver_spool_t
171
172 - Set files with the callweaver_spool_t type, if you want to store the
173 callweaver files under the /var/spool directory.
174
175
176
177 callweaver_var_lib_t
178
179 - Set files with the callweaver_var_lib_t type, if you want to store
180 the callweaver files under the /var/lib directory.
181
182
183
184 callweaver_var_run_t
185
186 - Set files with the callweaver_var_run_t type, if you want to store
187 the callweaver files under the /run or /var/run directory.
188
189
190
191 Note: File context can be temporarily modified with the chcon command.
192 If you want to permanently change the file context you need to use the
193 semanage fcontext command. This will modify the SELinux labeling data‐
194 base. You will need to use restorecon to apply the labels.
195
196
198 semanage fcontext can also be used to manipulate default file context
199 mappings.
200
201 semanage permissive can also be used to manipulate whether or not a
202 process type is permissive.
203
204 semanage module can also be used to enable/disable/install/remove pol‐
205 icy modules.
206
207 semanage boolean can also be used to manipulate the booleans
208
209
210 system-config-selinux is a GUI tool available to customize SELinux pol‐
211 icy settings.
212
213
215 This manual page was auto-generated using sepolicy manpage .
216
217
219 selinux(8), callweaver(8), semanage(8), restorecon(8), chcon(1), sepol‐
220 icy(8), setsebool(8)
221
222
223
224callweaver 20-05-05 callweaver_selinux(8)