All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Cc: xen-devel@lists.xenproject.org, julien.grall@linaro.org,
	Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH] xsm/flask: Handle policy load failures properly
Date: Tue, 24 Feb 2015 08:47:28 +0000	[thread overview]
Message-ID: <1424767648.32223.3.camel@citrix.com> (raw)
In-Reply-To: <54EB6930.2040703@tycho.nsa.gov>

On Mon, 2015-02-23 at 12:53 -0500, Daniel De Graaf wrote:
> When no policy is loaded, the FLASK policy is equivalent to an allow-all
> policy; see xen/xsm/flask/ss/services.c:security_compute_av where it
> bails out if !ss_initialized.  It could be considered as either enforcing
> or being permissive with an allow-all policy, but the actual access is
> the same.

Do you think anyone would want an option to be provided which causes Xen
to fail to boot if a proper policy isn't provided (and loaded)? Similar
to how iommu=force works.

I can see how osstest testcases for xsm might want this to avoid
accidentally testing with no policy, but not sure if it would be
considered generally useful enough to be added.

Ian.

  parent reply	other threads:[~2015-02-24  8:47 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 [this message]
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
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=1424767648.32223.3.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=julien.grall@linaro.org \
    --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.