From: "Tom Fortmann" <tfortmann@xcapesolutions.net>
To: "'Stephen Smalley'" <sds@tycho.nsa.gov>
Cc: <selinux@tycho.nsa.gov>
Subject: RE: FW: Current/Future Plans to Support Stacking LSM Modules
Date: Wed, 17 Jan 2007 14:09:25 -0600 [thread overview]
Message-ID: <006801c73a73$643b81e0$030a0a0a@ACER> (raw)
In-Reply-To: <1168977133.22731.149.camel@moss-spartans.epoch.ncsc.mil>
Stephen,
The security measures we are trying to implement require us to actually
inspect, and in some case modify, the application data flowing over a socket
connection. Our goal is to secure legacy server applications at the socket
layer. We have done some proof of concept work at the netfilter layer, but
the ultimate solution is better suited above the TCP/IP packet layer.
Does SELinux provide a mechanism for us to do this, and or does it call the
secondary LSM hooks that provide this type of access. Specifically the
socket_xxxx hooks?
Thanks again for all of your help,
Tom
Thomas Fortmann
Sr. Software Engineer
Xcape Solutions, Inc.
-----Original Message-----
From: Stephen Smalley [mailto:sds@tycho.nsa.gov]
Sent: Tuesday, January 16, 2007 1:52 PM
To: Tom Fortmann
Cc: selinux@tycho.nsa.gov
Subject: Re: FW: Current/Future Plans to Support Stacking LSM Modules
On Tue, 2007-01-16 at 13:41 -0600, Tom Fortmann wrote:
> Can you send me a pointer to the limited stacking that selinux supports?
http://www.nsa.gov/selinux/papers/module/x341.html
> I will join the LSM list. I started here because LSM already supports a
> basic stacking method. However, SELinux does not support the
> mod_reg_security call necessary to take advantage of this capability.
No, SELinux does support trivial stacking by implementing a
register_security hook, which is what mod_reg_security() calls. That is
used to combine SELinux with the Linux capabilities module.
> The product we are developing adds additional security at the application
> data layer. It is a commercial product so I can't say a lot, other then
to
> say that SELinux currently does not provide the additional features we are
> working on.
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 Smalley
National Security Agency
--
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-17 20:08 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
2007-01-17 20:09 ` Tom Fortmann [this message]
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='006801c73a73$643b81e0$030a0a0a@ACER' \
--to=tfortmann@xcapesolutions.net \
--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 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.