On 06/26/2018 07:09 AM, Andrew Cooper wrote:
The embedded policy is specific flask, so update the infrastructure to reflect
this.
Signed-off-by: Andrew Cooper <[email protected]>
This one actually has a history of being shared between FLASK and ACM (the
now-removed alternative to FLASK in earlier versions of Xen). However, the
current policy generation is very specific to FLASK, and it would be useful
to allow multiple security modules to each have their own default policy.
Overall, I think it's a useful change. Is there a reason you chose the
prefix "xsm_init_flask" over "xsm_flask_init"? The latter may be more
amenable to grepping.
Either way,
Acked-by: Daniel De Graaf <[email protected]>
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
