@@ -9,7 +9,7 @@ a fixed 32 bits to permission sets in 256 bit increments: *allowxperm*,
9
9
10
10
The rules for extended permissions are subject to the 'operation' they
11
11
perform with Policy version 30 and kernels from 4.3 supporting ioctl
12
- whitelisting (if required to be declared in modular policy, then
12
+ allowlists (if required to be declared in modular policy, then
13
13
libsepol 2.7 minimum is required).
14
14
15
15
** The common format for Extended Access Vector Rules are:**
@@ -74,7 +74,7 @@ Conditional Policy Statements
74
74
75
75
### * ioctl* Operation Rules
76
76
77
- Use cases and implementation details for ioctl command whitelisting are
77
+ Use cases and implementation details for ioctl command allowlists are
78
78
described in detail at
79
79
< http://marc.info/?l=selinux&m=143336061925628&w=2 > , with the final
80
80
policy format changes shown in the example below with a brief overview
@@ -118,9 +118,8 @@ tclass=udp_socket permissive=0
118
118
119
119
Notes:
120
120
121
- 1 . Important: The ioctl operation is not 'deny all' ioctl requests
122
- (hence whitelisting). It is targeted at the specific
123
- source/target/class set of ioctl commands. As no other * allowxperm*
121
+ 1 . Important: The ioctl operation is not 'deny all', it is targeted at the
122
+ specific source/target/class set of ioctl commands. As no other * allowxperm*
124
123
rules have been defined in the example, all other ioctl calls may
125
124
continue to use any valid request parameters (provided there are
126
125
* allow* rules for the * ioctl* permission).
0 commit comments