From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: gyurdiev@redhat.com, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: wish-list item for selinux policy analyss
Date: Thu, 30 Jun 2005 02:08:38 +0100 [thread overview]
Message-ID: <20050630010838.GF8415@lkcl.net> (raw)
In-Reply-To: <20050629165658.82487.qmail@web31609.mail.mud.yahoo.com>
On Wed, Jun 29, 2005 at 09:56:58AM -0700, Casey Schaufler wrote:
>
>
> --- Ivan Gyurdiev <gyurdiev@redhat.com> wrote:
>
> > > reason for this is to be able to fire up a
> > system, run
> > > it for a while (live) say oh a few months, and
> > then determine
> > > which bits of the selinux policy.conf have never
> > ever actually
> > > been used.
> >
> > I see several problems with this idea:
>
> 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?
wrong way round, casey.
intent of wish-list item is to be able to say "this door
hasn't been used for a year, let's brick it up".
not, as you imply, "this door hasn't been tried at all in a year, let's
now leave it wide open".
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.
next prev parent reply other threads:[~2005-06-30 1:00 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
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 [this message]
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=20050630010838.GF8415@lkcl.net \
--to=lkcl@lkcl.net \
--cc=casey@schaufler-ca.com \
--cc=gyurdiev@redhat.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.