All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: James Morris <jmorris@redhat.com>
Cc: netdev@oss.sgi.com, netfilter-devel@lists.netfilter.org,
	"David S. Miller" <davem@redhat.com>,
	Stephen Smalley <sds@epoch.ncsc.mil>
Subject: Re: [RFC] IPv4 Netfilter hook priorities for SELinux
Date: Tue, 6 Jan 2004 20:13:11 +0100	[thread overview]
Message-ID: <20040106191311.GH934@obroa-skai.de.gnumonks.org> (raw)
In-Reply-To: <Xine.LNX.4.44.0401061046390.7530-100000@thoron.boston.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 686 bytes --]

On Tue, Jan 06, 2004 at 11:01:03AM -0500, James Morris wrote:
 
> Does anyone have any objections to the patch below (which I'd propose for 
> 2.6.2), or other comments?

Thanks James, I am perfectly fine with your patch.  Feel free to put
them into netfilter_arp.h and netfilter_ipv6.h, too.

> - James

-- 
- Harald Welte <laforge@netfilter.org>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-01-06 19:13 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 [this message]
2004-01-06 20:05   ` James Morris
2004-01-07  5:36     ` David S. Miller

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=20040106191311.GH934@obroa-skai.de.gnumonks.org \
    --to=laforge@netfilter.org \
    --cc=davem@redhat.com \
    --cc=jmorris@redhat.com \
    --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.