From: Casey Schaufler <casey@schaufler-ca.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
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] V1 Remove SELinux dependencies from linux-audit via LSM
Date: Fri, 3 Aug 2007 09:33:19 -0700 (PDT) [thread overview]
Message-ID: <457110.86749.qm@web36606.mail.mud.yahoo.com> (raw)
In-Reply-To: <922084.93856.qm@web36605.mail.mud.yahoo.com>
--- Casey Schaufler <casey@schaufler-ca.com> wrote:
> > > diff -uprN -X linux-2.6.22-base/Documentation/dontdiff
> > > linux-2.6.22-base/include/linux/security.h
> > > linux-2.6.22-audit/include/linux/security.h
> > > --- linux-2.6.22-base/include/linux/security.h 2007-07-08
> > 16:32:17.000000000
> > > -0700
> > > +++ linux-2.6.22-audit/include/linux/security.h 2007-08-01
> > 20:14:18.000000000
> > > -0700
> > > @@ -35,6 +35,8 @@
> > > #include <net/flow.h>
> > >
> > > struct ctl_table;
> > > +struct audit_krule;
> > > +struct selinux_audit_rule;
> >
> > selinux_audit_rule in LSM interface?
>
> The structure needs a new name. Any objections to audit_rule_lsm?
> I'd suggest security_audit_rule, but that doesn't say anything about
> where to look to see how it gets used.
Actually, it's worse than that because an selinux_audit_rule really
is SELinux specific. Any problem with making the security_audit_rule
interfaces use a void * ? The audit code appears to be accomodating.
Casey Schaufler
casey@schaufler-ca.com
next prev parent reply other threads:[~2007-08-03 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 3:33 [PATCH][RFC] V1 Remove SELinux dependencies from linux-audit via LSM Casey Schaufler
2007-08-03 3:57 ` Casey Schaufler
2007-08-03 13:09 ` Stephen Smalley
2007-08-03 16:18 ` Casey Schaufler
2007-08-03 16:33 ` Casey Schaufler [this message]
2007-08-03 18:43 ` Stephen Smalley
2007-08-03 18:56 ` Casey Schaufler
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=457110.86749.qm@web36606.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