mirror of
https://github.com/xen-project/xen.git
synced 2026-10-28 10:11:27 +01:00
kaf24@firebug.cl.cam.ac.uk
ac5d4d868f
time (instead of at compile time). Allows a single xen.gz binary to run under different security policy types, which simplifies distributions considerably. To this end, we replace the current single compile switch in Config.mk with the following two: 1. ACM_SECURITY (y/n) if "n", then the ACM is not compiled and no security policies can be configured at boot time. If "y", then the ACM is compiled and can be configured into any of the available policy types (null, chwall, ste, chwall_ste) by specifying a valid boot policy .bin file in the grub boot configuration. 2. ACM_DEFAULT_SECURITY_POLICY (null / chwall / ste / chwall_ste) specifies the policy into which Xen defaults in the case that security is enabled but no boot policy file is specified, or the specified policy file is invalid (wrong version, magic, corrupted, ...) While the type of the enabled policy (null, ste, ...) is decided once during boot for the whole boot cycle, the policy instantiation can be changed during operation as usual with the security tools. Signed-off by: Tomas Lendacky <toml@us.ibm.com> Signed-off by: Reiner Sailer <sailer@us.ibm.com>
## # readme.txt <description to the xen access control architecture> # # Author: # Reiner Sailer 08/15/2005 <sailer@watson.ibm.com> # # # This file is a toc for information regarding # the access control policy and tools in Xen. ## 1. policy.txt: describes the general reasoning and examples for access control policies in Xen 2. install.txt describes the activation of the access control framework in Xen 3. example.txt describes the available tools for managing security policies in Xen and the tools to label domains