From: Casey Schaufler <casey@schaufler-ca.com>
To: sgrubb@redhat.com, viro@ftp.linux.org.uk, sds@tycho.nsa.gov
Cc: linux-audit@redhat.com
Subject: Audit, LSM, SELinux, and Smack
Date: Wed, 25 Jul 2007 13:19:26 -0700 (PDT) [thread overview]
Message-ID: <916629.84605.qm@web36613.mail.mud.yahoo.com> (raw)
I'm looking at getting audit into my Smack LSM module.
Stephen Smalley has suggested, and I concur, that this
may be the time to convert audit from using SELinux
specific interfaces to LSM based interfaces.
Before I start blasting away with patches, I want to
check and see if anyone else is looking into this.
There's a good chunk of work to be done for LSM, audit,
SELinux, and Smack. I also want to be sure that no one
will take umberage with the notion.
Thank you.
Casey Schaufler
casey@schaufler-ca.com
next reply other threads:[~2007-07-25 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 20:19 Casey Schaufler [this message]
2007-07-25 20:33 ` Audit, LSM, SELinux, and Smack Steve Grubb
2007-07-25 21:04 ` Casey Schaufler
2007-07-26 13:03 ` Stephen Smalley
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=916629.84605.qm@web36613.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=linux-audit@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=sgrubb@redhat.com \
--cc=viro@ftp.linux.org.uk \
/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