From: Steve Grubb <sgrubb@redhat.com>
To: casey@schaufler-ca.com
Cc: linux-audit@redhat.com, viro@ftp.linux.org.uk
Subject: Re: Audit, LSM, SELinux, and Smack
Date: Wed, 25 Jul 2007 16:33:56 -0400 [thread overview]
Message-ID: <200707251633.56990.sgrubb@redhat.com> (raw)
In-Reply-To: <916629.84605.qm@web36613.mail.mud.yahoo.com>
On Wednesday 25 July 2007 04:19:26 pm Casey Schaufler wrote:
> Before I start blasting away with patches, I want to
> check and see if anyone else is looking into this.
Nope.
> 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.
Well, I thought we were stable and could finish off the last couple kernel
items. :) If you are making big changes, be ware of performance impacts as
we've done a lot to make sure we don't slow everything down.
-Steve
next prev parent reply other threads:[~2007-07-25 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 20:19 Audit, LSM, SELinux, and Smack Casey Schaufler
2007-07-25 20:33 ` Steve Grubb [this message]
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=200707251633.56990.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=casey@schaufler-ca.com \
--cc=linux-audit@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