Farid,
The default policy track the Dom0/DomU usage model in the sense that one can
create and manage DomUs. That said, just because you can do something from
Dom0, doesn't mean that the sample policy supports that usage. An example
of the latter is kexec/kdump. The sample policy is a guide, you need to
develop your own policy goals and implement the policy accordingly.
You should be able to use the SELinux policy writing and analysis tools.
These tools depend only on the policy directory structure which the sample
XSM/Flask policy preserves with SELinux.
George
On 10/24/08 9:53 AM, "Ahmed, Farid" <Farid.Ahmed@xxxxxxxxxx> wrote:
> Hello everyone,
> I have two questions related to the XSM/Flask default policy.
> 1. Is there any documentation of what the default policy (or Dom0/DomU
> usage model) is supposed to do?
> 2. Is there any tool that may help the policy writing and especially
> testing XSM/Flask policy? How do we verify the policy is working?
>
> Thanks
> Farid
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel 
-- 
George S. Coker, II <gscoker@xxxxxxxxxxxxxx>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel