All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: [idea] multiple contexts.
Date: Tue, 27 Jul 2004 17:06:06 +0100	[thread overview]
Message-ID: <20040727160605.GG3392@lkcl.net> (raw)
In-Reply-To: <1090858323.24945.116.camel@moss-spartans.epoch.ncsc.mil>

On Mon, Jul 26, 2004 at 12:12:03PM -0400, Stephen Smalley wrote:
> On Sat, 2004-07-24 at 19:11, Luke Kenneth Casson Leighton wrote:
> > i'd like to propose an extension to the SE/Linux system: it's quite
> > straightforward and it could possibly be implemented in the macro
> > system - maybe, maybe not.
> > 
> > the ultimate aim is to help simplify the production of policies.
> > 
> > the idea is simple: to be able to have more than one context, and
> > to be able to make auditing decisions based on more than one context.
> 
> Not a good idea, and not necessary.  You can encode the entire call
> chain in a single security context using the domain transitions, 

 well, not entirely - not dynamically, anyway: at least i do not
 believe so.

 i thought originally that it would be possible to do what i envisaged
 with m4, by extending the policy language.


> and can
> then unwind as desired.  Fortunately, it sounds like the kdeinit problem
> is easily solved anyway.

 i also seek to limit the programs that a KDE user may run.

 if there is a simple way to do that which does not involve writing
 policy files for each and every single KDE program i intend to restrict
 users to use, i would be interested to hear it.

 l.


--
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:[~2004-07-27 15:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-24 23:11 [idea] multiple contexts Luke Kenneth Casson Leighton
2004-07-25  0:17 ` Russell Coker
2004-07-26 16:12 ` Stephen Smalley
2004-07-27 16:06   ` Luke Kenneth Casson Leighton [this message]
2004-07-27 17:33     ` Stephen Smalley
2004-07-27 18:23       ` Luke Kenneth Casson Leighton
2004-07-28 23:16         ` Erich Schubert
2004-07-29  1:00           ` Luke Kenneth Casson Leighton
2004-07-27 19:40     ` Valdis.Kletnieks
2004-07-27 21:28       ` Luke Kenneth Casson Leighton
2004-07-27 21:23         ` Valdis.Kletnieks
2004-07-27 21:49           ` Luke Kenneth Casson Leighton
2004-07-28 12:33         ` David Caplan
2004-07-28 14:37           ` Luke Kenneth Casson Leighton

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=20040727160605.GG3392@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=sds@epoch.ncsc.mil \
    --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.