From: Julien Grall <julien.grall@linaro.org>
To: Daniel De Graaf <dgdegra@tycho.nsa.gov>,
Ian Campbell <ian.campbell@citrix.com>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH] xsm/flask: Handle policy load failures properly
Date: Fri, 27 Feb 2015 14:03:26 +0000 [thread overview]
Message-ID: <54F0792E.6060503@linaro.org> (raw)
In-Reply-To: <54EC9E94.1050105@tycho.nsa.gov>
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 dummy (no XSM) policy, same as flask_enabled=0
> develop/permissive - a missing or broken policy does not panic
> enforce/enforcing/force - require policy to be loaded at boot time
> late/load - bootloader policy is not used; later loadpolicy is enforcing
>
> The default would be "permissive" as in the existing hypervisor. This
> would be more flexible, but I'm not sure it is worth breaking existing
> command lines and changing documentation to implement.
This look a good solution, having flask_enforcing without flask_enable
doesn't make much sense.
Although I don't know what is the policy about xen parameters. Maybe Ian
or Jan have an idea about it.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-02-27 14:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 16:11 [PATCH] xsm/flask: Handle policy load failures properly Daniel De Graaf
2015-02-23 16:48 ` Wei Liu
2015-02-23 17:53 ` Daniel De Graaf
2015-02-23 18:00 ` Wei Liu
2015-02-23 18:11 ` Andrew Cooper
2015-02-24 8:47 ` Ian Campbell
2015-02-24 9:31 ` Julien Grall
2015-02-24 9:39 ` Ian Campbell
2015-02-24 9:51 ` Julien Grall
2015-02-24 10:21 ` Ian Campbell
2015-02-24 15:53 ` Daniel De Graaf
2015-02-27 14:03 ` Julien Grall [this message]
2015-03-02 14:06 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54F0792E.6060503@linaro.org \
--to=julien.grall@linaro.org \
--cc=dgdegra@tycho.nsa.gov \
--cc=ian.campbell@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.