All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: Joshua Brindle <method@manicmethod.com>
Cc: vyekkirala@TrustedCS.com, John Wan <J.Wan@mbs.edu>,
	selinux@tycho.nsa.gov
Subject: Re: Would the SELinux  act as a TippingPoint IPS to block the nasty Trojan traffic?
Date: Wed, 11 Apr 2007 13:32:04 -0400	[thread overview]
Message-ID: <200704111332.04613.paul.moore@hp.com> (raw)
In-Reply-To: <461D1464.7070607@manicmethod.com>

On Wednesday, April 11 2007 1:01:24 pm Joshua Brindle wrote:
> Venkat Yekkirala wrote:
> > Just FYI-I did propose filtering in the filter table in the past,
> > and this has been on my todo list.
> >
> > "Implementation issues aside, lately I have been wondering about doing
> > something in the filter table using something we could call secfilter
> > or so.
> >
> > You would still use secmark to label the packets, but they (along with
> > any external labels) could get filtered in the secfilter module. This
> > way we could control what external labels could come thru from what
> > peers. For internal labels it would be more of an assurance thing. This
> > would also automatically take care of forwarding controls."
> >
> > More at: http://marc.info/?l=selinux&m=116232831800159&w=2
>
> so from what I gather the secfilter module would be querying the selinux
> policy to determine whether or not to drop something, that would mean a
> change in iptables changes the enforcement policy (not just the labeling
> policy as is the case now) which is a little disconcerting.

It a tradeoff: we gain the flexibility of the iptables packet/connection 
matching rules but we rely on the rules to be present.  It's very similar in 
principal to the discussions that have been going on with SECMARK; I suspect 
we can solve this problem in a similar manner.

> How does this work into the idea we had during the summit about SELinux
> having its own table? The table would presumably be a mangle table for
> labeling but could it also be a filter table? I'm not clear on what is
> possible in netfilter.

I'm not a netfilter expert myself, although I'm learning more and more about 
it each day.  I don't see how this couldn't fit into the proposed 
LSM/SELinux/security table in fact I think I mentioned something like this at 
one point (although, maybe it was just to myself).

-- 
paul moore
linux security @ hp

--
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.

  reply	other threads:[~2007-04-11 17:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10 11:30 Would the SELinux act as a TippingPoint IPS to block the nasty Trojan traffic? John Wan
2007-04-10 15:18 ` Paul Moore
2007-04-11  0:11   ` Joshua Brindle
2007-04-11  2:46     ` Paul Moore
2007-04-11  2:58       ` Joshua Brindle
2007-04-11 13:16         ` Paul Moore
2007-04-11 15:10           ` Venkat Yekkirala
2007-04-11 15:17             ` Paul Moore
2007-04-12 17:39               ` Venkat Yekkirala
2007-04-11 17:01             ` Joshua Brindle
2007-04-11 17:32               ` Paul Moore [this message]
2007-04-12 17:51                 ` Venkat Yekkirala
  -- strict thread matches above, loose matches on Subject: below --
2007-04-12 17:52 Venkat Yekkirala

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=200704111332.04613.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=J.Wan@mbs.edu \
    --cc=method@manicmethod.com \
    --cc=selinux@tycho.nsa.gov \
    --cc=vyekkirala@TrustedCS.com \
    /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.