1bitlbee_selinux(8) SELinux Policy bitlbee bitlbee_selinux(8)
2
6 bitlbee_selinux - Security Enhanced Linux Policy for the bitlbee pro‐
7 cesses
8
10 Security-Enhanced Linux secures the bitlbee processes via flexible
11 mandatory access control.
12 The bitlbee processes execute with the bitlbee_t SELinux type. You can
14 check if you have these processes running by executing the ps command
15 with the -Z qualifier.
16 For example:
18 ps -eZ | grep bitlbee_t
20
24 The bitlbee_t SELinux type can be entered via the bitlbee_exec_t file
25 type.
26 The default entrypoint paths for the bitlbee_t domain are the follow‐
28 ing:
29 /usr/bin/bip, /usr/sbin/bitlbee
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 bitlbee policy is very flexible allowing users to setup their bitlbee
40 processes in as secure a method as possible.
41 The following process types are defined for bitlbee:
43 bitlbee_t
45 Note: semanage permissive -a bitlbee_t can be used to make the process
47 type bitlbee_t permissive. SELinux does not deny access to permissive
48 process types, but the AVC (SELinux denials) messages are still gener‐
49 ated.
50
53 SELinux policy is customizable based on least access required. bitlbee
54 policy is extremely flexible and has several booleans that allow you to
55 manipulate the policy and run bitlbee with the tightest access possi‐
56 ble.
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 bitlbee_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 bitlbee_tmp_t
73 bitlbee_var_run_t
76 /var/run/bip(/.*)?
78 /var/run/bitlbee.pid
79 /var/run/bitlbee.sock
80 bitlbee_var_t
82 /var/lib/bitlbee(/.*)?
84 cluster_conf_t
86 /etc/cluster(/.*)?
88 cluster_var_lib_t
90 /var/lib/pcsd(/.*)?
92 /var/lib/cluster(/.*)?
93 /var/lib/openais(/.*)?
94 /var/lib/pengine(/.*)?
95 /var/lib/corosync(/.*)?
96 /usr/lib/heartbeat(/.*)?
97 /var/lib/heartbeat(/.*)?
98 /var/lib/pacemaker(/.*)?
99 cluster_var_run_t
101 /var/run/crm(/.*)?
103 /var/run/cman_.*
104 /var/run/rsctmp(/.*)?
105 /var/run/aisexec.*
106 /var/run/heartbeat(/.*)?
107 /var/run/pcsd-ruby.socket
108 /var/run/corosync-qnetd(/.*)?
109 /var/run/corosync-qdevice(/.*)?
110 /var/run/corosync.pid
111 /var/run/cpglockd.pid
112 /var/run/rgmanager.pid
113 /var/run/cluster/rgmanager.sk
114 krb5_host_rcache_t
116 /var/tmp/krb5_0.rcache2
118 /var/cache/krb5rcache(/.*)?
119 /var/tmp/nfs_0
120 /var/tmp/DNS_25
121 /var/tmp/host_0
122 /var/tmp/imap_0
123 /var/tmp/HTTP_23
124 /var/tmp/HTTP_48
125 /var/tmp/ldap_55
126 /var/tmp/ldap_487
127 /var/tmp/ldapmap1_0
128 root_t
130 /sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
132 /
133 /initrd
134
137 SELinux requires files to have an extended attribute to define the file
138 type.
139 You can see the context of a file using the -Z option to ls
141 Policy governs the access confined processes have to these files.
143 SELinux bitlbee policy is very flexible allowing users to setup their
144 bitlbee processes in as secure a method as possible.
145 STANDARD FILE CONTEXT
147 SELinux defines the file context types for the bitlbee, if you wanted
149 to store files with these types in a diffent paths, you need to execute
150 the semanage command to specify alternate labeling and then use re‐
151 storecon to put the labels on disk.
152 semanage fcontext -a -t bitlbee_var_run_t '/srv/mybitlbee_con‐
154 tent(/.*)?'
155 restorecon -R -v /srv/mybitlbee_content
156 Note: SELinux often uses regular expressions to specify labels that
158 match multiple files.
159 The following file types are defined for bitlbee:
161 bitlbee_conf_t
165 - Set files with the bitlbee_conf_t type, if you want to treat the
167 files as bitlbee configuration data, usually stored under the /etc di‐
168 rectory.
169 bitlbee_exec_t
173 - Set files with the bitlbee_exec_t type, if you want to transition an
175 executable to the bitlbee_t domain.
176 Paths:
179 /usr/bin/bip, /usr/sbin/bitlbee
180 bitlbee_initrc_exec_t
183 - Set files with the bitlbee_initrc_exec_t type, if you want to transi‐
185 tion an executable to the bitlbee_initrc_t domain.
186 bitlbee_log_t
190 - Set files with the bitlbee_log_t type, if you want to treat the data
192 as bitlbee log data, usually stored under the /var/log directory.
193 bitlbee_tmp_t
197 - Set files with the bitlbee_tmp_t type, if you want to store bitlbee
199 temporary files in the /tmp directories.
200 bitlbee_var_run_t
204 - Set files with the bitlbee_var_run_t type, if you want to store the
206 bitlbee files under the /run or /var/run directory.
207 Paths:
210 /var/run/bip(/.*)?, /var/run/bitlbee.pid, /var/run/bitlbee.sock
211 bitlbee_var_t
214 - Set files with the bitlbee_var_t type, if you want to store the bit
216 files under the /var directory.
217 Note: File context can be temporarily modified with the chcon command.
221 If you want to permanently change the file context you need to use the
222 semanage fcontext command. This will modify the SELinux labeling data‐
223 base. You will need to use restorecon to apply the labels.
224
227 semanage fcontext can also be used to manipulate default file context
228 mappings.
229 semanage permissive can also be used to manipulate whether or not a
231 process type is permissive.
232 semanage module can also be used to enable/disable/install/remove pol‐
234 icy modules.
235 semanage boolean can also be used to manipulate the booleans
237 system-config-selinux is a GUI tool available to customize SELinux pol‐
240 icy settings.
241
244 This manual page was auto-generated using sepolicy manpage .
245
248 selinux(8), bitlbee(8), semanage(8), restorecon(8), chcon(1), sepol‐
249 icy(8), setsebool(8)
250bitlbee 21-11-19 bitlbee_selinux(8)