All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: James Morris <jmorris@redhat.com>
Cc: laforge@netfilter.org, netdev@oss.sgi.com,
	netfilter-devel@lists.netfilter.org, sds@epoch.ncsc.mil
Subject: Re: [RFC] IPv4 Netfilter hook priorities for SELinux
Date: Tue, 6 Jan 2004 21:36:42 -0800	[thread overview]
Message-ID: <20040106213642.3b30f4bc.davem@redhat.com> (raw)
In-Reply-To: <Xine.LNX.4.44.0401061503180.8482-100000@thoron.boston.redhat.com>

On Tue, 6 Jan 2004 15:05:10 -0500 (EST)
James Morris <jmorris@redhat.com> wrote:

> Ok, here is the patch with support for IPv4 and IPv6.  I've not added 
> anything for ARP yet as SELinux does not have any ARP controls at this 
> stage (and probably won't in the near future).
> 
> Please apply.

Applied, thanks guys.

      reply	other threads:[~2004-01-07  5:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06 16:01 [RFC] IPv4 Netfilter hook priorities for SELinux James Morris
2004-01-06 19:13 ` Harald Welte
2004-01-06 20:05   ` James Morris
2004-01-07  5:36     ` David S. Miller [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=20040106213642.3b30f4bc.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=jmorris@redhat.com \
    --cc=laforge@netfilter.org \
    --cc=netdev@oss.sgi.com \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=sds@epoch.ncsc.mil \
    /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.