On Fri, 2015-02-27 at 14:03 +, Julien Grall wrote:
> Hi Daniel,
>
> On 24/02/15 15:53, Daniel De Graaf wrote:
> > This seems a reasonable solution if we don't want to change how the boot
> > parameters are set up.
> >
> > Another alternative would be to change flask_enforcing/flask_enabled to
Hi Daniel,
On 24/02/15 15:53, Daniel De Graaf wrote:
> This seems a reasonable solution if we don't want to change how the boot
> parameters are set up.
>
> Another alternative would be to change flask_enforcing/flask_enabled to
> a single "flask=" parameter with options:
> disabled - revert to
On 02/24/2015 05:21 AM, Ian Campbell wrote:
On Tue, 2015-02-24 at 09:51 +, Julien Grall wrote:
On 24/02/2015 09:39, Ian Campbell wrote:
On Tue, 2015-02-24 at 09:31 +, Julien Grall wrote:
On 24/02/2015 08:47, Ian Campbell wrote:
On Mon, 2015-02-23 at 12:53 -0500, Daniel De Graaf wrot
When the hypervisor is booted with an XSM policy containing an error
(such as a mismatched permission value), this error is mostly ignored
during boot. This causes FLASK to suspend security policy enforcement
until a policy is loaded, effectively allowing all access.
This patch adds a call to pan
