From: Casey Schaufler <casey@schaufler-ca.com>
To: Stephen Smalley <sds@tycho.nsa.gov>, casey@schaufler-ca.com
Cc: LSM List <linux-security-module@vger.kernel.org>,
SELinux List <selinux@tycho.nsa.gov>,
Audit List <linux-audit@redhat.com>
Subject: Re: [PATCH][RFC] V2 Remove SELinux dependencies from linux-audit via LSM
Date: Tue, 7 Aug 2007 10:44:30 -0700 (PDT) [thread overview]
Message-ID: <973639.58905.qm@web36608.mail.mud.yahoo.com> (raw)
In-Reply-To: <1186498030.26457.68.camel@moss-spartans.epoch.ncsc.mil>
--- Stephen Smalley <sds@tycho.nsa.gov> wrote:
> On Sun, 2007-08-05 at 17:03 -0700, Casey Schaufler wrote:
> > From: Casey Schaufler <casey@schaufler-ca.com>
> >
> > This patch interposes LSM interfaces between the audit system
> > and SELinux. This helps make SELinux a cleaner LSM and clarifies
> > the interfaces provided by the audit system. The audit system
> > no longer requires SELinux functions or data structures, making
> > it available for use by other LSMs.
> >
> > The audit system interfaces should now be useful to any LSM that
> > can provide secids and text string representations that match them.
> > The audit system uses secids only to map to those strings and
> > treats them as opaque data otherwise. Audit rule information that
> > is specific to an LSM is maintained through a void *.
> >
> > The SELinux code uses LSM interfaces to access the audit system,
> > with the exception of audit_rule_update_callout(), which is
> > intended to be called at the descretion of an LSM to update the
> > LSM specific rules.
> >
> > The LSM interface includes six new entries, four for audit and two
> > that supply secids from the LSM to networking and audit subsystems.
> > Also, there were several cases where SELinux code was being called
> > where LSM interfaces were more appropriate. These uses have been
> > repaired and the SELinux interfaces are no longer exported.
> >
> > Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
>
> Looks sane, but the patch is malformed again, so I can't apply it.
I have to change my posting infrastructure. Stoopid 21st century software.
> There are still a few places where you appear to be making
> sparse-induced cleanups of other code unrelated to this change, so make
> those separate patches (and be sure you aren't duplicating what is
> already upstream).
I'll just have to live with the warnings, I guess. Thank you.
> You've tested the resulting kernel? Built with a variety of configs?
Testing has been minimal (hence the [RFC]) because I don't want to
invest too much time in something that might not go anywhere. I will
work on an applyable patch posting and begin serious testing now that
someone who knows sanity when they see it (never one of my strong
points) has identified it as such. I have built it SELinux, Smack,
and neither, but only spent any serious run time with Smack.
Thank you.
Casey Schaufler
casey@schaufler-ca.com
prev parent reply other threads:[~2007-08-07 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 0:03 [PATCH][RFC] V2 Remove SELinux dependencies from linux-audit via LSM Casey Schaufler
2007-08-07 14:47 ` Stephen Smalley
2007-08-07 17:44 ` Casey Schaufler [this message]
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=973639.58905.qm@web36608.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=linux-audit@redhat.com \
--cc=linux-security-module@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox