blob: 9bb40680c3a915d1b37ac822f1e678127aa7df88 [file] [log] [blame]
Stephen Smalley2dd4e512012-01-04 12:33:27 -05001#########################################
2# MLS declarations
3#
4
5# Generate the desired number of sensitivities and categories.
6gen_sens(mls_num_sens)
7gen_cats(mls_num_cats)
8
9# Generate level definitions for each sensitivity and category.
10gen_levels(mls_num_sens,mls_num_cats)
11
12
13#################################################
14# MLS policy constraints
15#
16
17#
18# Process constraints
19#
20
21# Process transition: Require equivalence unless the subject is trusted.
22mlsconstrain process { transition dyntransition }
23 ((h1 eq h2 and l1 eq l2) or t1 == mlstrustedsubject);
24
25# Process read operations: No read up unless trusted.
26mlsconstrain process { getsched getsession getpgid getcap getattr ptrace share }
27 (l1 dom l2 or t1 == mlstrustedsubject);
28
29# Process write operations: No write down unless trusted.
30mlsconstrain process { sigkill sigstop signal setsched setpgid setcap setrlimit ptrace share }
31 (l1 domby l2 or t1 == mlstrustedsubject);
32
33#
34# Socket constraints
35#
36
37# These permissions are between the process and its local socket,
38# not between a process/socket and its peer.
39# Equivalence is the normal situation; anything else requires trust.
40mlsconstrain socket_class_set { read write create getattr setattr relabelfrom relabelto bind connect listen accept getopt setopt shutdown }
41 ((h1 eq h2 and l1 eq l2) or t1 == mlstrustedsubject or t2 == mlstrustedsubject);
42
43# Datagram send: Sender must be dominated by receiver unless one of them is
44# trusted.
45mlsconstrain unix_dgram_socket { sendto }
46 (l1 domby l2 or t1 == mlstrustedsubject or t2 == mlstrustedsubject);
47
48# Stream connect: Client must be equivalent to server unless one of them
49# is trusted.
50mlsconstrain unix_stream_socket { connectto }
51 (l1 eq l2 or t1 == mlstrustedsubject or t2 == mlstrustedsubject);
52
53#
54# Directory/file constraints
55#
56
57# Create/relabel operations: Subject must be equivalent to object unless
58# the subject is trusted. Also, files should always be single-level.
59# Do NOT exempt mlstrustedobject types from this constraint.
60mlsconstrain dir_file_class_set { create relabelfrom relabelto }
61 (l2 eq h2 and (l1 eq l2 or t1 == mlstrustedsubject));
62
63# Read operations: Subject must dominate object unless the subject
64# or the object is trusted.
65mlsconstrain dir { read getattr search }
66 (l1 dom l2 or t1 == mlstrustedsubject or t2 == mlstrustedobject);
67
68mlsconstrain { file lnk_file sock_file chr_file blk_file } { read getattr execute }
69 (l1 dom l2 or t1 == mlstrustedsubject or t2 == mlstrustedobject);
70
71# Write operations: Subject must be dominated by the object unless the
72# subject or the object is trusted.
73mlsconstrain dir { write setattr rename add_name remove_name reparent rmdir }
74 (l1 domby l2 or t1 == mlstrustedsubject or t2 == mlstrustedobject);
75
76mlsconstrain { file lnk_file sock_file chr_file blk_file } { write setattr append unlink link rename }
77 (l1 domby l2 or t1 == mlstrustedsubject or t2 == mlstrustedobject);
78
79# Special case for FIFOs.
80# These can be unnamed pipes, in which case they will be labeled with the
81# creating process' label. Thus we also have an exemption when the "object"
82# is a MLS trusted subject and can receive data at any level.
83mlsconstrain fifo_file { read getattr }
84 (l1 dom l2 or t1 == mlstrustedsubject or t2 == mlstrustedobject or t2 == mlstrustedsubject);
85
86mlsconstrain fifo_file { write setattr append unlink link rename }
87 (l1 domby l2 or t1 == mlstrustedsubject or t2 == mlstrustedobject or t2 == mlstrustedsubject);
88
89#
90# IPC constraints
91#
92
93# Create/destroy: equivalence or trusted.
94mlsconstrain ipc_class_set { create destroy }
95 (l2 eq h2 and (l1 eq l2 or t1 == mlstrustedsubject));
96
97# Read ops: No read up unless trusted.
98mlsconstrain ipc_class_set r_ipc_perms
99 (l1 dom l2 or t1 == mlstrustedsubject);
100
101# Write ops: No write down unless trusted.
102mlsconstrain ipc_class_set w_ipc_perms
103 (l1 domby l2 or t1 == mlstrustedsubject);
104
105#
106# Binder IPC constraints
107#
108# Presently commented out, as apps are expected to call one another.
109# This would only make sense if apps were assigned categories
110# based on allowable communications rather than per-app categories.
111#mlsconstrain binder call
112# (l1 eq l2 or t1 == mlstrustedsubject or t2 == mlstrustedsubject);