From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: SE-Linux <selinux@tycho.nsa.gov>
Subject: wish-list item for selinux policy analyss
Date: Wed, 29 Jun 2005 03:13:49 +0100 [thread overview]
Message-ID: <20050629021349.GA10219@lkcl.net> (raw)
dear selinux people,
on my wish-list for selinux is a means to tell, at runtime,
which avc messages have been utilised. not when - if.
the equivalent of code coverage analysis tools.
i envisage this to be implemented - hand-waving - by a single
bit which is marked in the in-kernel-memory store of selinux avc
policy, for reasons of minimising impact on run-time performance
(i believe that tying something into the avc audit logging
system, would be too slow).
the 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.
track them down, and remove them from the selinux source policy.
... via analysis of the policy.conf, back to the macros from
whence they came.
l.
--
--
<a href="http://lkcl.net">http://lkcl.net</a>
--
--
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 reply other threads:[~2005-06-29 2:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 2:13 Luke Kenneth Casson Leighton [this message]
2005-06-29 15:27 ` wish-list item for selinux policy analyss 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
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=20050629021349.GA10219@lkcl.net \
--to=lkcl@lkcl.net \
--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.