From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Cc: xen-devel@lists.xenproject.org, cardoe@cardoe.com,
Ian.Jackson@eu.citrix.com, andrew.cooper3@citrix.com
Subject: Re: [PATCH v2] flask: change default state to enforcing
Date: Fri, 8 Apr 2016 10:55:24 -0400 [thread overview]
Message-ID: <20160408145524.GA32299@char.us.oracle.com> (raw)
In-Reply-To: <1459971359-5902-1-git-send-email-dgdegra@tycho.nsa.gov>
On Wed, Apr 06, 2016 at 03:35:59PM -0400, Daniel De Graaf wrote:
> The previous default of "permissive" is meant for developing or
> debugging a disaggregated system. However, this default makes it too
> easy to accidentally boot a machine in this state, which does not place
> any restrictions on guests. This is not suitable for normal systems
> because any guest can perform any operation (including operations like
> rebooting the machine, kexec, and reading or writing another domain's
> memory).
>
> This change will cause the boot to fail if you do not specify an XSM
> policy during boot; if you need to load a policy from dom0, use the
> "flask=late" boot parameter.
>
> Original patch by Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>; modified
> to also change the default value of flask_enforcing so that the policy
> is not still in permissive mode. This also removes the (no longer
> documented) command line argument directly changing that variable since
> it has been superseded by the flask= parameter.
>
> Signed-off-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Reviewed and applied.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-04-08 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 19:35 [PATCH v2] flask: change default state to enforcing Daniel De Graaf
2016-04-08 14:55 ` Konrad Rzeszutek Wilk [this message]
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=20160408145524.GA32299@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=dgdegra@tycho.nsa.gov \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).