All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: Eamon Walsh <ewalsh@tycho.nsa.gov>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	selinux@tycho.nsa.gov, jmorris@namei.org,
	Steve G <linux_4ever@yahoo.com>
Subject: Re: [PATCH -v2] kernel: selinux: policy selectable handling of	unknown classes and perms
Date: Thu, 20 Sep 2007 15:18:55 -0400	[thread overview]
Message-ID: <1190315935.3451.112.camel@localhost.localdomain> (raw)
In-Reply-To: <46F03EC1.3010900@tycho.nsa.gov>

On Tue, 2007-09-18 at 17:10 -0400, Eamon Walsh wrote:
> Stephen Smalley wrote:
> > On Thu, 2007-09-13 at 11:05 -0400, Eric Paris wrote:
> >> Allow policy to select, in much the same way as it selects MLS support,
> >> how the kernel should handle access decisions which contain either
> >> unknown classes or unknown permissions in known classes.  The three
> >> choices are
> >>
> >> 0 - Deny unknown security access. (default)
> >> 2 - reject loading policy if it does not contain all definitions
> >> 4 - allow unknown security access
> >>
> >> The policy's choice is exported (with a value of 0,2,4) to userspace
> >> through /selinuxfs/handle_unknown 
> > 
> > Eamon, does this userspace interface work for you to use in the
> > userspace AVC?  Do you want the integer value like this or would you
> > prefer the "reject", "deny", or "allow" string that is displayed by the
> > kernel in its log message at load policy time?
> > 
> 
> Numeric values are fine, but the tristate is a little cumbersome.  Would 
> it be possible to split this into two boolean files, one reporting 
> zero/one for "don't reject/reject" and one reporting zero/one for 
> "allow/deny"?

Is this really necessary?  Are you really trying to say you don't want
to know about reject and if I put it in another file you can just ignore
it?  I'm fine with that if userspace just plain doesn't care about it,
I'll just make one allow/deny boolean.  I don't want to create another
selinuxfs file if it is going to be useless.  If 2 files are actually
useful and needed I'm willing to do that too, or maybe one file which
outputs 2 boolean flags.

cat unknown
0 0

> Also, I quickly scanned the patch and I didn't see any netlink code.  I 
> need a netlink notification delivered to userspace when the values 
> change.  This could be added to the policyload message, or a new 
> separate message type, or both.

Its not there.  I guess I'll look at this now.


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2007-09-20 19:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 15:05 [PATCH -v2] kernel: selinux: policy selectable handling of unknown classes and perms Eric Paris
2007-09-18 16:28 ` Stephen Smalley
2007-09-18 16:42   ` Eric Paris
2007-09-18 17:26     ` Stephen Smalley
2007-09-18 21:10   ` Eamon Walsh
2007-09-20 19:18     ` Eric Paris [this message]
2007-09-21  1:23       ` Eamon Walsh
2007-09-21 13:17         ` Eric Paris

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=1190315935.3451.112.camel@localhost.localdomain \
    --to=eparis@redhat.com \
    --cc=ewalsh@tycho.nsa.gov \
    --cc=jmorris@namei.org \
    --cc=linux_4ever@yahoo.com \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    /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.