On 07/07/16 16:36, Daniel De Graaf wrote:
On 07/06/2016 12:19 PM, anshul makkar wrote:
On 06/07/16 16:59, Daniel De Graaf wrote:
On 07/06/2016 11:34 AM, anshul makkar wrote:
Hi,
It allows the resource to be added and removed by the source domain to
target domain, but its use by target
On 07/06/2016 12:19 PM, anshul makkar wrote:
On 06/07/16 16:59, Daniel De Graaf wrote:
On 07/06/2016 11:34 AM, anshul makkar wrote:
Hi,
It allows the resource to be added and removed by the source domain to
target domain, but its use by target domain is blocked.
This rule only mandates the
On 06/07/16 16:59, Daniel De Graaf wrote:
On 07/06/2016 11:34 AM, anshul makkar wrote:
Hi,
It allows the resource to be added and removed by the source domain to
target domain, but its use by target domain is blocked.
This rule only mandates the use of resource_type for resource types. If
On 07/06/2016 11:34 AM, anshul makkar wrote:
Hi,
Default XSM policy doesn't allow the use of unlabeled PCI resources that have
been passed through to target domain.
xen.te
# Resources must be declared using . resource_type
neverallow * ~resource_type:resource use;
It allows the resource to
Hi,
Default XSM policy doesn't allow the use of unlabeled PCI resources that
have been passed through to target domain.
xen.te
# Resources must be declared using . resource_type
neverallow * ~resource_type:resource use;
It allows the resource to be added and removed by the source domain
