xsm/flask: add domain relabel support
authorDaniel De Graaf <dgdegra@tycho.nsa.gov>
Mon, 17 Sep 2012 20:12:21 +0000 (21:12 +0100)
committerDaniel De Graaf <dgdegra@tycho.nsa.gov>
Mon, 17 Sep 2012 20:12:21 +0000 (21:12 +0100)
commitfdbb35aaea778f8457728cde49d5918916c33470
treec414a0a7c1aab313f5c085f26624d86809b3ad88
parentf6db6c7b888e0cdb42d653bd551f5d6490b33ad5
xsm/flask: add domain relabel support

This adds the ability to change a domain's XSM label after creation.
The new label will be used for all future access checks; however,
existing event channels and memory mappings will remain valid even if
their creation would be denied by the new label.

With appropriate security policy and hooks in the domain builder, this
can be used to create domains that the domain builder does not have
access to after building. It can also be used to allow a domain to
drop privileges - for example, prior to launching a user-supplied
kernel loaded by a pv-grub stubdom.

Signed-off-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Committed-by: Keir Fraser <keir@xen.org>
tools/flask/policy/policy/flask/access_vectors
tools/flask/policy/policy/flask/security_classes
tools/flask/policy/policy/modules/xen/xen.te
xen/include/public/xsm/flask_op.h
xen/xsm/flask/flask_op.c
xen/xsm/flask/include/av_perm_to_string.h
xen/xsm/flask/include/av_permissions.h
xen/xsm/flask/include/class_to_string.h
xen/xsm/flask/include/flask.h