From: Casey Schaufler <casey@schaufler-ca.com>
To: Stephen Smalley <sds@tycho.nsa.gov>,
Tom Fortmann <tfortmann@xcapesolutions.net>
Cc: selinux@tycho.nsa.gov, linux-security-module@vger.kernel.org
Subject: Re: FW: Current/Future Plans to Support Stacking LSM Modules
Date: Tue, 16 Jan 2007 12:31:58 -0800 (PST) [thread overview]
Message-ID: <251786.34008.qm@web36612.mail.mud.yahoo.com> (raw)
In-Reply-To: <1168977133.22731.149.camel@moss-spartans.epoch.ncsc.mil>
--- Stephen Smalley <sds@tycho.nsa.gov> wrote:
> If you are adding additional security at the
> application data layer,
> then you can do that in userspace, and use SELinux
> Type Enforcement to
> make it unbypassable and tamperproof. You don't
> need to change the
> kernel.
Stephen, you can't possibly know that kernel
changes aren't required from the information
provided. The information provided appears
to be intentionally imprecise. (not a good
idea in the community, BTW) You may prove
correct in the end (you often are) but you're
jumping the SELinux Uber Alas gun.
Casey Schaufler
casey@schaufler-ca.com
--
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 prev parent reply other threads:[~2007-01-16 20:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 19:41 FW: Current/Future Plans to Support Stacking LSM Modules Tom Fortmann
2007-01-16 19:52 ` Stephen Smalley
2007-01-16 20:31 ` Tom Fortmann
2007-01-16 20:31 ` Casey Schaufler [this message]
2007-01-17 20:09 ` Tom Fortmann
2007-01-18 12:48 ` Stephen Smalley
2007-01-18 17:13 ` Tom Fortmann
2007-01-19 15:31 ` Stephen Smalley
2007-01-19 15:57 ` Tom Fortmann
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=251786.34008.qm@web36612.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=linux-security-module@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=tfortmann@xcapesolutions.net \
/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.