1callweaver_selinux(8) SELinux Policy callweaver callweaver_selinux(8)
2
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 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 For example:
18 ps -eZ | grep callweaver_t
20
24 The callweaver_t SELinux type can be entered via the callweaver_exec_t
25 file type.
26 The default entrypoint paths for the callweaver_t domain are the fol‐
28 lowing:
29 /usr/sbin/callweaver
31
33 SELinux defines process types (domains) for each process running on the
34 system
35 You can see the context of a process using the -Z option to ps
37 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 The following process types are defined for callweaver:
43 callweaver_t
45 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
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 ac‐
56 cess possible.
57 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 setsebool -P fips_mode 1
64
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 callweaver_spool_t
73 /var/spool/callweaver(/.*)?
75 callweaver_var_lib_t
77 /var/lib/callweaver(/.*)?
79 callweaver_var_run_t
81 /var/run/callweaver(/.*)?
83 cluster_conf_t
85 /etc/cluster(/.*)?
87 cluster_var_lib_t
89 /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 cluster_var_run_t
100 /var/run/crm(/.*)?
102 /var/run/cman_.*
103 /var/run/rsctmp(/.*)?
104 /var/run/aisexec.*
105 /var/run/heartbeat(/.*)?
106 /var/run/pcsd-ruby.socket
107 /var/run/corosync-qnetd(/.*)?
108 /var/run/corosync-qdevice(/.*)?
109 /var/run/corosync.pid
110 /var/run/cpglockd.pid
111 /var/run/rgmanager.pid
112 /var/run/cluster/rgmanager.sk
113 krb5_host_rcache_t
115 /var/tmp/krb5_0.rcache2
117 /var/cache/krb5rcache(/.*)?
118 /var/tmp/nfs_0
119 /var/tmp/DNS_25
120 /var/tmp/host_0
121 /var/tmp/imap_0
122 /var/tmp/HTTP_23
123 /var/tmp/HTTP_48
124 /var/tmp/ldap_55
125 /var/tmp/ldap_487
126 /var/tmp/ldapmap1_0
127 root_t
129 /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
131 /
132 /initrd
133
136 SELinux requires files to have an extended attribute to define the file
137 type.
138 You can see the context of a file using the -Z option to ls
140 Policy governs the access confined processes have to these files.
142 SELinux callweaver policy is very flexible allowing users to setup
143 their callweaver processes in as secure a method as possible.
144 STANDARD FILE CONTEXT
146 SELinux defines the file context types for the callweaver, if you
148 wanted to store files with these types in a diffent paths, you need to
149 execute the semanage command to specify alternate labeling and then use
150 restorecon to put the labels on disk.
151 semanage fcontext -a -t callweaver_spool_t '/srv/mycallweaver_con‐
153 tent(/.*)?'
154 restorecon -R -v /srv/mycallweaver_content
155 Note: SELinux often uses regular expressions to specify labels that
157 match multiple files.
158 The following file types are defined for callweaver:
160 callweaver_exec_t
164 - Set files with the callweaver_exec_t type, if you want to transition
166 an executable to the callweaver_t domain.
167 callweaver_initrc_exec_t
171 - Set files with the callweaver_initrc_exec_t type, if you want to
173 transition an executable to the callweaver_initrc_t domain.
174 callweaver_log_t
178 - Set files with the callweaver_log_t type, if you want to treat the
180 data as callweaver log data, usually stored under the /var/log direc‐
181 tory.
182 callweaver_spool_t
186 - Set files with the callweaver_spool_t type, if you want to store the
188 callweaver files under the /var/spool directory.
189 callweaver_var_lib_t
193 - Set files with the callweaver_var_lib_t type, if you want to store
195 the callweaver files under the /var/lib directory.
196 callweaver_var_run_t
200 - Set files with the callweaver_var_run_t type, if you want to store
202 the callweaver files under the /run or /var/run directory.
203 Note: File context can be temporarily modified with the chcon command.
207 If you want to permanently change the file context you need to use the
208 semanage fcontext command. This will modify the SELinux labeling data‐
209 base. You will need to use restorecon to apply the labels.
210
213 semanage fcontext can also be used to manipulate default file context
214 mappings.
215 semanage permissive can also be used to manipulate whether or not a
217 process type is permissive.
218 semanage module can also be used to enable/disable/install/remove pol‐
220 icy modules.
221 semanage boolean can also be used to manipulate the booleans
223 system-config-selinux is a GUI tool available to customize SELinux pol‐
226 icy settings.
227
230 This manual page was auto-generated using sepolicy manpage .
231
234 selinux(8), callweaver(8), semanage(8), restorecon(8), chcon(1), sepol‐
235 icy(8), setsebool(8)
236callweaver 23-02-03 callweaver_selinux(8)