All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Ron Kuris <rk@unify.com>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
	gyurdiev@redhat.com, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: wish-list item for selinux policy analyss
Date: Thu, 30 Jun 2005 02:05:26 +0100	[thread overview]
Message-ID: <20050630010526.GE8415@lkcl.net> (raw)
In-Reply-To: <42C2DC80.8070904@unify.com>

On Wed, Jun 29, 2005 at 10:38:08AM -0700, Ron Kuris wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Casey Schaufler wrote:
> 
> | I say amen to points 1-3. I add ...
> |
> | 4) A derived policy set will only tell you what the programs do,
> | not what they are intended to do. Should I leave doors unlocked
> | because burglers attempt to use them? If no burgler tries my door
> | for a year does that mean having a lock on my door is unnecessary?
> 
> I think the logic here is backwards.  

 yep.  selinux is "MAC".

> a year, then that door is a candidate for becoming a wall instead of a
> door.  Otherwise, you end up in a maze of twisty passages, where
> nobody knows what doors are needed and why.  Fewer doors means less
> memory also, which can be important for embedded systems.
> 
> I think this wish-list item doesn't tell you what you can remove from
> a policy.  However, it might tell you which rules are candidates to be
> changed to a "deny" rule (or lack of an "allow" rule really).  

 absolutely.

 that was the intent.


--
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:[~2005-06-30  0:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29  2:13 wish-list item for selinux policy analyss Luke Kenneth Casson Leighton
2005-06-29 15:27 ` Ivan Gyurdiev
2005-06-29 16:56   ` Casey Schaufler
2005-06-29 17:38     ` Ron Kuris
2005-06-30  1:05       ` Luke Kenneth Casson Leighton [this message]
2005-06-30  1:04         ` Casey Schaufler
2005-06-30 11:49           ` Luke Kenneth Casson Leighton
2005-06-30  1:08     ` Luke Kenneth Casson Leighton
2005-06-30  1:10       ` Casey Schaufler
2005-06-30 11:47         ` Luke Kenneth Casson Leighton
2005-06-30  0:37   ` Luke Kenneth Casson Leighton
2005-06-30  7:05     ` Ivan Gyurdiev
2005-06-30 12:16       ` Stephen Smalley
2005-06-30 20:51       ` Luke Kenneth Casson Leighton
2005-06-30 12:53 ` Joshua Brindle

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=20050630010526.GE8415@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=casey@schaufler-ca.com \
    --cc=gyurdiev@redhat.com \
    --cc=rk@unify.com \
    --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.