From: Paul Moore <paul.moore@hp.com>
To: selinux@tycho.nsa.gov
Subject: Re: [RFC PATCH] SELinux: Add network ingress and egress control permission checks
Date: Tue, 8 Jan 2008 12:03:16 -0500 [thread overview]
Message-ID: <200801081203.16131.paul.moore@hp.com> (raw)
In-Reply-To: <Xine.LNX.4.64.0801070922120.21625@us.intercode.com.au>
On Sunday 06 January 2008 5:22:25 pm James Morris wrote:
> On Fri, 4 Jan 2008, Paul Moore wrote:
> > This patch implements packet ingress/egress controls for SELinux
> > which allow SELinux security policy to control the flow of all IPv4
> > and IPv6 packets into and out of the system. Currently SELinux
> > does not have proper control over forwarded packets and this patch
> > corrects this problem.
> >
> > Special thanks to Venkat Yekkirala <vyekkirala@trustedcs.com> whose
> > earlier work on this topic eventually led to this patch.
> >
> > Signed-off-by: Paul Moore <paul.moore@hp.com>
>
> Please send this to netdev for review.
For those of you who don't follow netdev, this approach got a thumbs up
so it looks like we are still on track for 2.6.25.
--
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.
prev parent reply other threads:[~2008-01-08 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 0:34 [RFC PATCH] New take on the ingress/egress patch Paul Moore
2008-01-05 0:34 ` [RFC PATCH] SELinux: Add network ingress and egress control permission checks Paul Moore
2008-01-06 22:22 ` James Morris
2008-01-07 12:50 ` Paul Moore
2008-01-08 17:03 ` Paul Moore [this message]
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=200801081203.16131.paul.moore@hp.com \
--to=paul.moore@hp.com \
--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.