1telepathy_mission_coSnEtLrionlu_xsePloilniucxy(8t)elepathyt_emliespsaitohny__cmoinstsriooln_control_selinux(8)
2
3
4

NAME

6       telepathy_mission_control_selinux  - Security Enhanced Linux Policy for
7       the telepathy_mission_control processes
8

DESCRIPTION

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

ENTRYPOINTS

24       The  telepathy_mission_control_t  SELinux  type  can be entered via the
25       telepathy_mission_control_exec_t file type.
26
27       The default entrypoint paths for the telepathy_mission_control_t domain
28       are the following:
29
30       /usr/libexec/mission-control-5
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       telepathy_mission_control  policy  is  very  flexible allowing users to
40       setup their telepathy_mission_control processes in as secure  a  method
41       as possible.
42
43       The following process types are defined for telepathy_mission_control:
44
45       telepathy_mission_control_t
46
47       Note: semanage permissive -a telepathy_mission_control_t can be used to
48       make the process type telepathy_mission_control_t  permissive.  SELinux
49       does  not deny access to permissive process types, but the AVC (SELinux
50       denials) messages are still generated.
51
52

BOOLEANS

54       SELinux policy is customizable based on least access required.  telepa‐
55       thy_mission_control  policy is extremely flexible and has several bool‐
56       eans that allow you to manipulate the  policy  and  run  telepathy_mis‐
57       sion_control with the tightest access possible.
58
59
60
61       If you want to allow all domains to execute in fips_mode, you must turn
62       on the fips_mode boolean. Enabled by default.
63
64       setsebool -P fips_mode 1
65
66
67
68       If you want to allow system to run with  NIS,  you  must  turn  on  the
69       nis_enabled boolean. Disabled by default.
70
71       setsebool -P nis_enabled 1
72
73
74

MANAGED FILES

76       The  SELinux  process type telepathy_mission_control_t can manage files
77       labeled with the following file types.  The paths listed  are  the  de‐
78       fault paths for these file types.  Note the processes UID still need to
79       have DAC permissions.
80
81       cache_home_t
82
83            /root/.cache(/.*)?
84            /home/[^/]+/.nv(/.*)?
85            /home/[^/]+/.cache(/.*)?
86
87       cifs_t
88
89
90       config_home_t
91
92            /root/.kde(/.*)?
93            /root/.xine(/.*)?
94            /root/.config(/.*)?
95            /var/run/user/[^/]*/dconf(/.*)?
96            /root/.Xdefaults
97            /home/[^/]+/.kde(/.*)?
98            /home/[^/]+/.xine(/.*)?
99            /home/[^/]+/.config(/.*)?
100            /home/[^/]+/.cache/dconf(/.*)?
101            /home/[^/]+/.Xdefaults
102
103       ecryptfs_t
104
105            /home/[^/]+/.Private(/.*)?
106            /home/[^/]+/.ecryptfs(/.*)?
107
108       fusefs_t
109
110            /var/run/user/[^/]*/gvfs
111
112       krb5_host_rcache_t
113
114            /var/tmp/krb5_0.rcache2
115            /var/cache/krb5rcache(/.*)?
116            /var/tmp/nfs_0
117            /var/tmp/DNS_25
118            /var/tmp/host_0
119            /var/tmp/imap_0
120            /var/tmp/HTTP_23
121            /var/tmp/HTTP_48
122            /var/tmp/ldap_55
123            /var/tmp/ldap_487
124            /var/tmp/ldapmap1_0
125
126       nfs_t
127
128
129       telepathy_gabble_cache_home_t
130
131            /home/[^/]+/.cache/wocky(/.*)?
132            /home/[^/]+/.cache/telepathy/gabble(/.*)?
133            /home/[^/]+/.cache/telepathy/avatars/gabble(/.*)?
134
135       telepathy_mission_control_cache_home_t
136
137            /home/[^/]+/.cache/.mc_connections
138
139       telepathy_mission_control_data_home_t
140
141            /home/[^/]+/.local/share/telepathy/mission-control(/.*)?
142
143       telepathy_mission_control_home_t
144
145            /home/[^/]+/.mission-control(/.*)?
146
147       telepathy_mission_control_tmp_t
148
149
150

FILE CONTEXTS

152       SELinux requires files to have an extended attribute to define the file
153       type.
154
155       You can see the context of a file using the -Z option to ls
156
157       Policy  governs  the  access  confined  processes  have to these files.
158       SELinux telepathy_mission_control  policy  is  very  flexible  allowing
159       users to setup their telepathy_mission_control processes in as secure a
160       method as possible.
161
162       STANDARD FILE CONTEXT
163
164       SELinux defines the file context types for  the  telepathy_mission_con‐
165       trol, if you wanted to store files with these types in a diffent paths,
166       you need to execute the semanage command to specify alternate  labeling
167       and then use restorecon to put the labels on disk.
168
169       semanage    fcontext   -a   -t   telepathy_mission_control_cache_home_t
170       '/srv/mytelepathy_mission_control_content(/.*)?'
171       restorecon -R -v /srv/mytelepathy_mission_control_content
172
173       Note: SELinux often uses regular expressions  to  specify  labels  that
174       match multiple files.
175
176       The following file types are defined for telepathy_mission_control:
177
178
179
180       telepathy_mission_control_cache_home_t
181
182       -  Set  files  with the telepathy_mission_control_cache_home_t type, if
183       you want to store telepathy mission control cache files  in  the  users
184       home directory.
185
186
187
188       telepathy_mission_control_data_home_t
189
190       - Set files with the telepathy_mission_control_data_home_t type, if you
191       want to store telepathy mission control data files in  the  users  home
192       directory.
193
194
195
196       telepathy_mission_control_exec_t
197
198       - Set files with the telepathy_mission_control_exec_t type, if you want
199       to transition an executable to the telepathy_mission_control_t domain.
200
201
202
203       telepathy_mission_control_home_t
204
205       - Set files with the telepathy_mission_control_home_t type, if you want
206       to store telepathy mission control files in the users home directory.
207
208
209
210       telepathy_mission_control_tmp_t
211
212       -  Set files with the telepathy_mission_control_tmp_t type, if you want
213       to store telepathy mission control temporary files in the /tmp directo‐
214       ries.
215
216
217
218       Note:  File context can be temporarily modified with the chcon command.
219       If you want to permanently change the file context you need to use  the
220       semanage fcontext command.  This will modify the SELinux labeling data‐
221       base.  You will need to use restorecon to apply the labels.
222
223

COMMANDS

225       semanage fcontext can also be used to manipulate default  file  context
226       mappings.
227
228       semanage  permissive  can  also  be used to manipulate whether or not a
229       process type is permissive.
230
231       semanage module can also be used to enable/disable/install/remove  pol‐
232       icy modules.
233
234       semanage boolean can also be used to manipulate the booleans
235
236
237       system-config-selinux is a GUI tool available to customize SELinux pol‐
238       icy settings.
239
240

AUTHOR

242       This manual page was auto-generated using sepolicy manpage .
243
244

SEE ALSO

246       selinux(8), telepathy_mission_control(8),  semanage(8),  restorecon(8),
247       chcon(1), sepolicy(8), setsebool(8)
248
249
250
251telepathy_mission_control          21-11-19telepathy_mission_control_selinux(8)
Impressum