jabberd_router_selinux(8)

1jabberd_router_selinux(8)SELinux Policy jabberd_routerjabberd_router_selinux(8)
2
3
4

NAME

6       jabberd_router_selinux  -  Security  Enhanced Linux Policy for the jab‐
7       berd_router processes
8

DESCRIPTION

10       Security-Enhanced Linux secures the jabberd_router processes via flexi‐
11       ble mandatory access control.
12
13       The  jabberd_router processes execute with the jabberd_router_t SELinux
14       type. You can check if you have these processes  running  by  executing
15       the ps command with the -Z qualifier.
16
17       For example:
18
19       ps -eZ | grep jabberd_router_t
20
21
22

ENTRYPOINTS

24       The   jabberd_router_t  SELinux  type  can  be  entered  via  the  jab‐
25       berd_router_exec_t file type.
26
27       The default entrypoint paths for the jabberd_router_t  domain  are  the
28       following:
29
30       /usr/bin/c2s, /usr/bin/router
31

PROCESS TYPES

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       jabberd_router  policy  is  very flexible allowing users to setup their
40       jabberd_router processes in as secure a method as possible.
41
42       The following process types are defined for jabberd_router:
43
44       jabberd_router_t
45
46       Note: semanage permissive -a jabberd_router_t can be used to  make  the
47       process  type jabberd_router_t permissive. SELinux does not deny access
48       to permissive process types, but the AVC (SELinux denials) messages are
49       still generated.
50
51

BOOLEANS

53       SELinux  policy  is  customizable based on least access required.  jab‐
54       berd_router policy is extremely flexible and has several booleans  that
55       allow  you  to  manipulate  the  policy and run jabberd_router with the
56       tightest access possible.
57
58
59
60       If you want to allow all daemons to write corefiles to /, you must turn
61       on the daemons_dump_core boolean. Disabled by default.
62
63       setsebool -P daemons_dump_core 1
64
65
66
67       If  you  want  to enable cluster mode for daemons, you must turn on the
68       daemons_enable_cluster_mode boolean. Enabled by default.
69
70       setsebool -P daemons_enable_cluster_mode 1
71
72
73
74       If you want to allow all daemons to use tcp wrappers, you must turn  on
75       the daemons_use_tcp_wrapper boolean. Disabled by default.
76
77       setsebool -P daemons_use_tcp_wrapper 1
78
79
80
81       If  you  want to allow all daemons the ability to read/write terminals,
82       you must turn on the daemons_use_tty boolean. Disabled by default.
83
84       setsebool -P daemons_use_tty 1
85
86
87
88       If you want to deny any process from ptracing or  debugging  any  other
89       processes,  you  must  turn  on  the  deny_ptrace  boolean.  Enabled by
90       default.
91
92       setsebool -P deny_ptrace 1
93
94
95
96       If you want to allow any process  to  mmap  any  file  on  system  with
97       attribute  file_type,  you must turn on the domain_can_mmap_files bool‐
98       ean. Enabled by default.
99
100       setsebool -P domain_can_mmap_files 1
101
102
103
104       If you want to allow all domains write to kmsg_device, while kernel  is
105       executed  with  systemd.log_target=kmsg parameter, you must turn on the
106       domain_can_write_kmsg boolean. Disabled by default.
107
108       setsebool -P domain_can_write_kmsg 1
109
110
111
112       If you want to allow all domains to use other domains file descriptors,
113       you must turn on the domain_fd_use boolean. Enabled by default.
114
115       setsebool -P domain_fd_use 1
116
117
118
119       If  you  want to allow all domains to have the kernel load modules, you
120       must  turn  on  the  domain_kernel_load_modules  boolean.  Disabled  by
121       default.
122
123       setsebool -P domain_kernel_load_modules 1
124
125
126
127       If you want to allow all domains to execute in fips_mode, you must turn
128       on the fips_mode boolean. Enabled by default.
129
130       setsebool -P fips_mode 1
131
132
133
134       If you want to enable reading of urandom for all domains, you must turn
135       on the global_ssp boolean. Disabled by default.
136
137       setsebool -P global_ssp 1
138
139
140
141       If  you  want  to allow confined applications to run with kerberos, you
142       must turn on the kerberos_enabled boolean. Enabled by default.
143
144       setsebool -P kerberos_enabled 1
145
146
147
148       If you want to allow system to run with  NIS,  you  must  turn  on  the
149       nis_enabled boolean. Disabled by default.
150
151       setsebool -P nis_enabled 1
152
153
154

MANAGED FILES

156       The SELinux process type jabberd_router_t can manage files labeled with
157       the following file types.  The paths listed are the default  paths  for
158       these  file  types.  Note the processes UID still need to have DAC per‐
159       missions.
160
161       cluster_conf_t
162
163            /etc/cluster(/.*)?
164
165       cluster_var_lib_t
166
167            /var/lib/pcsd(/.*)?
168            /var/lib/cluster(/.*)?
169            /var/lib/openais(/.*)?
170            /var/lib/pengine(/.*)?
171            /var/lib/corosync(/.*)?
172            /usr/lib/heartbeat(/.*)?
173            /var/lib/heartbeat(/.*)?
174            /var/lib/pacemaker(/.*)?
175
176       cluster_var_run_t
177
178            /var/run/crm(/.*)?
179            /var/run/cman_.*
180            /var/run/rsctmp(/.*)?
181            /var/run/aisexec.*
182            /var/run/heartbeat(/.*)?
183            /var/run/corosync-qnetd(/.*)?
184            /var/run/corosync-qdevice(/.*)?
185            /var/run/cpglockd.pid
186            /var/run/corosync.pid
187            /var/run/rgmanager.pid
188            /var/run/cluster/rgmanager.sk
189
190       jabberd_var_lib_t
191
192            /var/lib/jabberd(/.*)?
193
194       root_t
195
196            /sysroot/ostree/deploy/.*-atomic.*/deploy(/.*)?
197            /
198            /initrd
199
200

FILE CONTEXTS

202       SELinux requires files to have an extended attribute to define the file
203       type.
204
205       You can see the context of a file using the -Z option to ls
206
207       Policy  governs  the  access  confined  processes  have to these files.
208       SELinux jabberd_router policy is very flexible allowing users to  setup
209       their jabberd_router processes in as secure a method as possible.
210
211       The following file types are defined for jabberd_router:
212
213
214
215       jabberd_router_exec_t
216
217       - Set files with the jabberd_router_exec_t type, if you want to transi‐
218       tion an executable to the jabberd_router_t domain.
219
220
221       Paths:
222            /usr/bin/c2s, /usr/bin/router
223
224
225       Note: File context can be temporarily modified with the chcon  command.
226       If  you want to permanently change the file context you need to use the
227       semanage fcontext command.  This will modify the SELinux labeling data‐
228       base.  You will need to use restorecon to apply the labels.
229
230

COMMANDS

232       semanage  fcontext  can also be used to manipulate default file context
233       mappings.
234
235       semanage permissive can also be used to manipulate  whether  or  not  a
236       process type is permissive.
237
238       semanage  module can also be used to enable/disable/install/remove pol‐
239       icy modules.
240
241       semanage boolean can also be used to manipulate the booleans
242
243
244       system-config-selinux is a GUI tool available to customize SELinux pol‐
245       icy settings.
246
247

AUTHOR

249       This manual page was auto-generated using sepolicy manpage .
250
251