Lines Matching refs:this
6 a security model using this framework (at the time of writing, it is the only
25 this document.
54 The following interfaces are covered by this statement. Interfaces
62 All subops except the following are covered by this statement. (That
72 All subops are covered by this statement. (That is, no subops are
77 The following subops are covered by this statement. subops not listed
87 TMEM_CONTROL, are covered by this statement.
91 Due to this existing policy all TMEM Ops are already subject to
126 and FLASK inside 'Common Features'; this change requires a make clean and
139 different types (domU_t would be the type in this example). For simple policies,
144 It relies on the SELinux compiler "checkpolicy"; if this is available, the
175 this for the most common case of groups that can communicate internally but not
184 this by only creating one domain per type, this solution significantly limits
185 the flexibility of the type system. Another method to address this issue is to
187 current domain or on other domains; however, this significantly increases the
188 necessary number of permissions and complicates the XSM hooks. Instead, this is
195 domain's label as the source and target. The result of this computation is used
196 as the target when the domain accesses itself. In the example policy, this
205 target domain as the source and the device model domain as the target: this
323 source/destination is printed to the log, so labeling devices using this method