xsm, argo: XSM control for argo message send operation

Default policy: allow.

Signed-off-by: Christopher Clark <christopher.clark6@baesystems.com>
Reviewed-by: Paul Durrant <paul.durrant@citrix.com>
Acked-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Tested-by: Chris Patterson <pattersonc@ainfosec.com>
Release-acked-by: Juergen Gross <jgross@suse.com>
This commit is contained in:
Christopher Clark authored and Jan Beulich committed 2019-02-07 14:26:11 +01:00
1 parent 23d160faeb
commit 4c0526b739
7 files changed
+37 -3

No files matched your search

+4 -3
View File
@@ -6,10 +6,11 @@ allow domain_type xen_t:xen tmem_op;
allow domain_type xen_t:xen2 pmu_use;
# Allow all domains:
# to register single-sender (unicast) rings to partner with any domain; and
# to register any-sender (wildcard) rings that can be sent to by any domain.
# to register single-sender (unicast) rings to partner with any domain;
# to register any-sender (wildcard) rings that can be sent to by any domain;
# and send messages to rings.
allow domain_type xen_t:argo { register_any_source };
allow domain_type domain_type:argo { register_single_source };
allow domain_type domain_type:argo { send register_single_source };
# Allow guest console output to the serial console. This is used by PV Linux
# and stub domains for early boot output, so don't audit even when we deny it.
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.