From: Eamon Walsh <ewalsh@tycho.nsa.gov>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: "Christopher J. PeBenito" <cpebenito@tresys.com>,
Joshua Brindle <jbrindle@tresys.com>,
SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: object class discovery userland
Date: Tue, 29 May 2007 15:06:27 -0400 [thread overview]
Message-ID: <465C79B3.6050501@tycho.nsa.gov> (raw)
In-Reply-To: <1180462767.3340.116.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Wed, 2007-05-23 at 14:17 +0000, Christopher J. PeBenito wrote:
>> The object manager will also have to be modified to get the new class
>> and perm values on a policy reload.
>
> Why not just require them to remain stable at runtime, and require a
> restart of the object manager if you are going to change them? Allowing
> them to change at any time will introduce a fair amount of
> complexity/overhead at runtime.
>
I'm fine with this, however I think it should be the kernel's job to
enforce the stability of the values. The policyload should fail if the
values are changing.
Perhaps this could be a configurable "experimental" versus "production"
option, or perhaps userspace object managers could somehow register with
the kernel which will then refuse to change the values if any are
currently running.
--
Eamon Walsh <ewalsh@tycho.nsa.gov>
National Security Agency
--
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.
next prev parent reply other threads:[~2007-05-29 19:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 14:01 object class discovery userland Christopher J. PeBenito
2007-04-20 14:04 ` Joshua Brindle
2007-04-20 14:17 ` Karl MacMillan
2007-04-20 14:23 ` Joshua Brindle
2007-04-20 14:22 ` Karl MacMillan
2007-04-20 14:27 ` Joshua Brindle
2007-04-20 14:58 ` KaiGai Kohei
2007-04-20 15:32 ` Christopher J. PeBenito
2007-04-20 16:54 ` Eamon Walsh
2007-04-20 17:02 ` Eamon Walsh
2007-04-20 17:19 ` Christopher J. PeBenito
2007-04-23 14:33 ` Stephen Smalley
2007-04-23 14:43 ` Joshua Brindle
2007-04-23 14:58 ` Stephen Smalley
2007-05-23 14:17 ` Christopher J. PeBenito
2007-05-23 18:51 ` Eamon Walsh
2007-05-24 23:46 ` Eamon Walsh
2007-05-24 23:55 ` Joshua Brindle
2007-05-25 0:00 ` Joshua Brindle
2007-05-25 21:10 ` Eamon Walsh
2007-05-25 22:36 ` Joshua Brindle
2007-05-29 17:50 ` Eamon Walsh
2007-05-29 18:36 ` Stephen Smalley
2007-05-29 18:24 ` Stephen Smalley
2007-05-29 19:17 ` Eamon Walsh
2007-05-30 2:20 ` KaiGai Kohei
2007-05-30 20:01 ` Eamon Walsh
2007-05-31 13:28 ` KaiGai Kohei
2007-06-01 17:18 ` Eamon Walsh
2007-05-29 18:19 ` Stephen Smalley
2007-05-29 19:06 ` Eamon Walsh [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-23 16:33 Nick Nam
2007-04-23 16:36 Nick Nam
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=465C79B3.6050501@tycho.nsa.gov \
--to=ewalsh@tycho.nsa.gov \
--cc=cpebenito@tresys.com \
--cc=jbrindle@tresys.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.