Difference between revisions of "PolicyStatements"
(New page: = Policy Support Statements = This section contains language statements used to support policy. == module Statement == This statement is mandatory for loadable modules (non-base) and must...) |
|||
Line 1: | Line 1: | ||
− | = Policy Support Statements = | + | = Modular Policy Support Statements = |
− | This section contains language statements used to support policy. | + | This section contains language statements used to support policy modules. |
− | == module | + | == module == |
This statement is mandatory for loadable modules (non-base) and must be the first line of any module policy source file. The identifier should not conflict with other module names within the overall policy, otherwise it will over-write an existing module when loaded via the semodule command. The semodule -l command can be used to list all active modules within the policy. | This statement is mandatory for loadable modules (non-base) and must be the first line of any module policy source file. The identifier should not conflict with other module names within the overall policy, otherwise it will over-write an existing module when loaded via the semodule command. The semodule -l command can be used to list all active modules within the policy. | ||
Line 9: | Line 9: | ||
module module_name version_number; | module module_name version_number; | ||
</pre> | </pre> | ||
− | |||
'''Where:''' | '''Where:''' | ||
− | {|border="1" | + | |
− | |module | + | {| border="1" |
− | |The module keyword. | + | | module |
+ | | The module keyword. | ||
|- | |- | ||
− | |module_name | + | | module_name |
− | |The module name. | + | | The module name. |
|- | |- | ||
− | |version_number | + | | version_number |
− | |The module version number in M.m.m format (where M = major version number and m = minor version numbers). | + | | The module version number in M.m.m format (where M = major version number and m = minor version numbers). |
|} | |} | ||
Line 28: | Line 28: | ||
'''The statement is valid in:''' | '''The statement is valid in:''' | ||
− | {|border="1" | + | |
+ | {| border="1" | ||
|<center>'''Monolithic Policy'''</center> | |<center>'''Monolithic Policy'''</center> | ||
|<center>'''Base Policy'''</center> | |<center>'''Base Policy'''</center> | ||
Line 34: | Line 35: | ||
|- | |- | ||
− | |<center>No</center> | + | | <center>'''No'''</center> |
− | |<center>No</center> | + | | <center>'''No'''</center> |
− | |<center>Yes</center> | + | | <center>'''Yes'''</center> |
+ | |} | ||
− | | | + | |
− | |<center> | + | {| border="1" |
− | |<center> | + | | <center>[[ConditionalStatements#if | if Statement]]</center> |
− | |<center> | + | | <center>[[PolicyStatements#optional | optional Statement]] </center> |
+ | | <center>[[PolicyStatements#require | require Statement]] </center> | ||
|- | |- | ||
− | |<center>No</center> | + | | <center>'''No'''</center> |
− | |<center>No</center> | + | | <center>'''No'''</center> |
− | |<center>No</center> | + | | <center>'''No'''</center> |
|} | |} | ||
Line 53: | Line 56: | ||
'''Example:''' | '''Example:''' | ||
<pre> | <pre> | ||
− | + | # Using the module statement to define a loadable module called | |
− | + | # bind with a version 1.0.0: | |
module bind 1.8.0; | module bind 1.8.0; | ||
</pre> | </pre> | ||
− | == require | + | == require == |
The require statement is used for two reasons: | The require statement is used for two reasons: | ||
− | |||
# Within loadable module policy source files to indicate what policy components are required from an external source file (i.e. they are not explicitly defined in this module but elsewhere). The examples below show the usage. | # Within loadable module policy source files to indicate what policy components are required from an external source file (i.e. they are not explicitly defined in this module but elsewhere). The examples below show the usage. | ||
− | # Within a base policy source file, but only if preceded by the optional | + | # Within a base policy source file, but only if preceded by the [[#optional | optional]] statement to indicate what policy components are required from an external source file (i.e. they are not explicitly defined in the base policy but elsewhere). The examples below show the usage. |
'''The statement definition is:''' | '''The statement definition is:''' | ||
Line 71: | Line 73: | ||
'''Where:''' | '''Where:''' | ||
− | {|border="1" | + | |
− | |require | + | {| border="1" |
− | |The require keyword. | + | | require |
+ | | The require keyword. | ||
|- | |- | ||
− | |require_list | + | | require_list |
− | |One or more specific statement keywords with their required identifiers in a semi-colon (<nowiki>;</nowiki>) separated list enclosed within braces ({}). | + | | One or more specific statement keywords with their required identifiers in a semi-colon (<nowiki>;</nowiki>) separated list enclosed within braces ({}). |
The valid statement keywords are: | The valid statement keywords are: | ||
− | |||
* role, type, attribute, user, bool, sensitivity and category. The keyword is followed by one or more identifiers in a comma (,) separated list, with the last entry being terminated with a semi-colon (<nowiki>;</nowiki>). | * role, type, attribute, user, bool, sensitivity and category. The keyword is followed by one or more identifiers in a comma (,) separated list, with the last entry being terminated with a semi-colon (<nowiki>;</nowiki>). | ||
* class. The class keyword is followed by a single object class identifier and one or more permissions. Multiple permissions consist of a space separated list enclosed within braces ({}). The list is then terminated with a semi-colon (<nowiki>;</nowiki>). | * class. The class keyword is followed by a single object class identifier and one or more permissions. Multiple permissions consist of a space separated list enclosed within braces ({}). The list is then terminated with a semi-colon (<nowiki>;</nowiki>). | ||
Line 90: | Line 92: | ||
'''The statement is valid in:''' | '''The statement is valid in:''' | ||
− | {|border="1" | + | |
+ | {| border="1" | ||
|<center>'''Monolithic Policy'''</center> | |<center>'''Monolithic Policy'''</center> | ||
|<center>'''Base Policy'''</center> | |<center>'''Base Policy'''</center> | ||
Line 96: | Line 99: | ||
|- | |- | ||
− | |<center>No</center> | + | | <center>'''No'''</center> |
− | |<center>Yes - But only if proceeded by the optional Statement.</center> | + | | <center>'''Yes - But only if proceeded by the [[#optional | optional]] Statement.'''</center> |
− | |<center>Yes</center> | + | | <center>'''Yes'''</center> |
+ | |} | ||
− | |||
− | |||
− | |||
− | |||
− | | | + | {| border="1" |
− | |<center> | + | | <center>[[ConditionalStatements#if | if Statement]]</center> |
− | |<center> | + | | <center>[[PolicyStatements#optional | optional Statement]] </center> |
− | |<center> | + | | <center>[[PolicyStatements#require | require Statement]] </center> |
+ | |- | ||
+ | | <center>'''Yes - But only if proceeded by the [[#optional | optional]] Statement.'''</center> | ||
+ | | <center>'''Yes'''</center> | ||
+ | | <center>'''No'''</center> | ||
|} | |} | ||
Line 115: | Line 119: | ||
'''Examples:''' | '''Examples:''' | ||
<pre> | <pre> | ||
− | + | # A series of require statements showing various entries: | |
require { | require { | ||
− | + | role system_r; | |
− | + | class security { compute_av compute_create compute_member | |
− | + | check_context load_policy compute_relabel compute_user | |
− | + | setenforce setbool setsecparam setcheckreqprot }; | |
+ | class capability2 { mac_override mac_admin }; | ||
} | } | ||
− | + | # | |
require { | require { | ||
− | + | attribute direct_run_init, direct_init, direct_init_entry; | |
− | + | type initrc_t; | |
− | + | role system_r; | |
− | + | attribute daemon; | |
} | } | ||
− | + | # | |
require { | require { | ||
− | + | type nscd_t, nscd_var_run_t; | |
− | + | class nscd { getserv getpwd getgrp gethost shmempwd shmemgrp | |
− | + | shmemhost shmemserv }; | |
} | } | ||
</pre> | </pre> | ||
− | == optional | + | == optional == |
− | The optional statement is used to indicate what policy statements may or may not be present in the final compiled policy. The statements will be included in the policy only if all statements within the optional { rule list } can be expanded successfully, this is generally achieved by using a require Statement at the start of the list. | + | The optional statement is used to indicate what policy statements may or may not be present in the final compiled policy. The statements will be included in the policy only if all statements within the optional { rule list } can be expanded successfully, this is generally achieved by using a [[#require | require]] Statement at the start of the list. |
'''The statement definition is:''' | '''The statement definition is:''' | ||
<pre> | <pre> | ||
− | optional { rule_list } | + | optional { rule_list } [ else { rule_list } ] |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
</pre> | </pre> | ||
'''Where:''' | '''Where:''' | ||
− | |||
− | |||
− | |||
− | | | + | {| border="1" |
− | | | + | | optional |
− | | | + | | The optional keyword. |
|- | |- | ||
− | |else | + | | rule_list |
− | |An optional else keyword. | + | | One or more statements enclosed within braces ({}). |
+ | |- | ||
+ | | else | ||
+ | | An optional else keyword. | ||
|- | |- | ||
− | |rule_list | + | | rule_list |
− | |As the rule_list above. | + | | As the rule_list above. |
|} | |} | ||
Line 173: | Line 174: | ||
'''The statement is valid in:''' | '''The statement is valid in:''' | ||
− | {|border="1" | + | |
+ | {| border="1" | ||
|<center>'''Monolithic Policy'''</center> | |<center>'''Monolithic Policy'''</center> | ||
|<center>'''Base Policy'''</center> | |<center>'''Base Policy'''</center> | ||
Line 179: | Line 181: | ||
|- | |- | ||
− | |<center>No</center> | + | | <center>'''No'''</center> |
− | |<center>Yes</center> | + | | <center>'''Yes'''</center> |
− | |<center>Yes</center> | + | | <center>'''Yes'''</center> |
+ | |} | ||
− | | | + | |
− | |<center> | + | {| border="1" |
− | |<center> | + | | <center>[[ConditionalStatements#if | if Statement]]</center> |
− | |<center> | + | | <center>[[PolicyStatements#optional | optional Statement]] </center> |
+ | | <center>[[PolicyStatements#require | require Statement]] </center> | ||
|- | |- | ||
− | |<center>Yes</center> | + | | <center>'''Yes'''</center> |
− | |<center>Yes</center> | + | | <center>'''Yes'''</center> |
− | |<center>Yes</center> | + | | <center>'''Yes'''</center> |
|} | |} | ||
Line 198: | Line 202: | ||
'''Examples:''' | '''Examples:''' | ||
<pre> | <pre> | ||
− | + | # Use of optional block. | |
optional { | optional { | ||
− | + | require { | |
− | + | type unconfined_t; | |
− | + | } # end require | |
− | + | allow acct_t unconfined_t:fd use; | |
− | + | ||
− | + | ||
} # end optional | } # end optional | ||
</pre> | </pre> | ||
<pre> | <pre> | ||
− | + | # Use of optional / else blocks. | |
optional { | optional { | ||
− | + | require { | |
− | + | type ping_t, ping_exec_t; | |
− | + | } # end require | |
+ | allow dhcpc_t ping_exec_t:file { getattr read execute }; | ||
+ | ..... | ||
− | + | require { | |
− | + | type netutils_t, netutils_exec_t; | |
− | + | } # end require | |
− | + | allow dhcpc_t netutils_exec_t:file { getattr read execute }; | |
− | + | ..... | |
− | + | type_transition dhcpc_t netutils_exec_t:process netutils_t; | |
− | + | ... | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
} else { | } else { | ||
− | + | allow dhcpc_t self:capability setuid; | |
− | + | ..... | |
− | + | } # end optional / else block | |
− | } # end optional | + | |
</pre> | </pre> | ||
− | = | + | {| style="width: 100%;" border="0" |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
|- | |- | ||
− | | | + | | [[NetworkStatements | '''Previous''']] |
− | | | + | | <center>[[NewUsers | '''Home''']]</center> |
− | + | | <center>[[XENStatements | '''Next''']]</center> | |
|} | |} | ||
− | + | ---- | |
− | + | <references/> | |
− | + | ||
− | + | ||
− | + | ||
− | + | [[Category:Notebook]] | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + |
Latest revision as of 15:12, 28 January 2015
Modular Policy Support Statements
This section contains language statements used to support policy modules.
module
This statement is mandatory for loadable modules (non-base) and must be the first line of any module policy source file. The identifier should not conflict with other module names within the overall policy, otherwise it will over-write an existing module when loaded via the semodule command. The semodule -l command can be used to list all active modules within the policy.
The statement definition is:
module module_name version_number;
Where:
module | The module keyword. |
module_name | The module name. |
version_number | The module version number in M.m.m format (where M = major version number and m = minor version numbers). |
The statement is valid in:
|
|
|
|
|
|
|
|
|
Example:
# Using the module statement to define a loadable module called # bind with a version 1.0.0: module bind 1.8.0;
require
The require statement is used for two reasons:
- Within loadable module policy source files to indicate what policy components are required from an external source file (i.e. they are not explicitly defined in this module but elsewhere). The examples below show the usage.
- Within a base policy source file, but only if preceded by the optional statement to indicate what policy components are required from an external source file (i.e. they are not explicitly defined in the base policy but elsewhere). The examples below show the usage.
The statement definition is:
require { rule_list }
Where:
require | The require keyword. |
require_list | One or more specific statement keywords with their required identifiers in a semi-colon (;) separated list enclosed within braces ({}).
The valid statement keywords are:
The examples below show these in detail. |
The statement is valid in:
|
|
|
|
|
|
|
|
|
Examples:
# A series of require statements showing various entries: require { role system_r; class security { compute_av compute_create compute_member check_context load_policy compute_relabel compute_user setenforce setbool setsecparam setcheckreqprot }; class capability2 { mac_override mac_admin }; } # require { attribute direct_run_init, direct_init, direct_init_entry; type initrc_t; role system_r; attribute daemon; } # require { type nscd_t, nscd_var_run_t; class nscd { getserv getpwd getgrp gethost shmempwd shmemgrp shmemhost shmemserv }; }
optional
The optional statement is used to indicate what policy statements may or may not be present in the final compiled policy. The statements will be included in the policy only if all statements within the optional { rule list } can be expanded successfully, this is generally achieved by using a require Statement at the start of the list.
The statement definition is:
optional { rule_list } [ else { rule_list } ]
Where:
optional | The optional keyword. |
rule_list | One or more statements enclosed within braces ({}). |
else | An optional else keyword. |
rule_list | As the rule_list above. |
The statement is valid in:
|
|
|
|
|
|
|
|
|
Examples:
# Use of optional block. optional { require { type unconfined_t; } # end require allow acct_t unconfined_t:fd use; } # end optional
# Use of optional / else blocks. optional { require { type ping_t, ping_exec_t; } # end require allow dhcpc_t ping_exec_t:file { getattr read execute }; ..... require { type netutils_t, netutils_exec_t; } # end require allow dhcpc_t netutils_exec_t:file { getattr read execute }; ..... type_transition dhcpc_t netutils_exec_t:process netutils_t; ... } else { allow dhcpc_t self:capability setuid; ..... } # end optional / else block
Previous | |
|