All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Joshua Brindle <jbrindle@tresys.com>,
	Eric Paris <eparis@parisplace.org>,
	selinux@tycho.nsa.gov, James Morris <jmorris@redhat.com>
Subject: Re: [RFC] Ability to allow unknown class and permissions
Date: Tue, 05 Dec 2006 08:59:16 -0500	[thread overview]
Message-ID: <45757B34.5050209@mentalrootkit.com> (raw)
In-Reply-To: <1165325510.15979.6.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Mon, 2006-12-04 at 16:05 -0500, Karl MacMillan wrote:
>> Stephen Smalley wrote:
>> See above.
> 
> You still need validation in the kernel, and the policy would still lack
> kernel classes and/or permissions unless libsemanage/libsepol is also
> inserting fake entries for the missing ones, so how would the kernel
> handle missing classes and permissions?  How would it know that
> userspace had already padded the avtab for them?
> 
> I'm unconvinced that this approach is simpler overall compared to direct
> kernel implementation at load time.
> 

You may be right and I don't feel that strongly about it. I was really 
just hoping that the discovery interface would finally get done.

Karl

--
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:[~2006-12-05 13:59 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-01 16:06 [RFC] Ability to allow unknown class and permissions Eric Paris
2006-12-01 17:18 ` Stephen Smalley
2006-12-01 18:41 ` Stephen Smalley
2006-12-02  3:28   ` Joshua Brindle
2006-12-04 14:46     ` Stephen Smalley
2006-12-04 15:11       ` Joshua Brindle
2006-12-04 15:24         ` Stephen Smalley
2006-12-04 18:13           ` Joshua Brindle
2006-12-04 18:49             ` Eric Paris
2006-12-04 19:39               ` Stephen Smalley
2006-12-04 20:06                 ` Karl MacMillan
2006-12-04 20:11                   ` Joshua Brindle
2006-12-04 20:15                     ` Karl MacMillan
2006-12-04 20:18                       ` Joshua Brindle
2006-12-04 20:25                         ` Karl MacMillan
2006-12-04 20:28                           ` Joshua Brindle
2006-12-04 20:25                             ` Stephen Smalley
2006-12-04 20:34                               ` Karl MacMillan
2006-12-04 20:44                                 ` Stephen Smalley
2006-12-04 21:05                                   ` Karl MacMillan
2006-12-05 13:31                                     ` Stephen Smalley
2006-12-05 13:59                                       ` Karl MacMillan [this message]
2006-12-04 20:33                             ` Karl MacMillan
2006-12-04 21:19                               ` Joshua Brindle
2006-12-04 21:34                                 ` Karl MacMillan
2006-12-04 23:20                                   ` Joshua Brindle
2006-12-05 13:41                                     ` Stephen Smalley
2006-12-05 13:33                                 ` Stephen Smalley

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=45757B34.5050209@mentalrootkit.com \
    --to=kmacmillan@mentalrootkit.com \
    --cc=eparis@parisplace.org \
    --cc=jbrindle@tresys.com \
    --cc=jmorris@redhat.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.