netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masahide NAKAMURA <nakam@linux-ipv6.org>
To: netfilter-devel@lists.netfilter.org
Cc: rdenis@simphalempin.com, usagi-core@linux-ipv6.org,
	Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>,
	Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Subject: Re: [NETFILTER]: ip6_tables: Support MH match.
Date: Sat, 10 Feb 2007 17:32:13 +0900	[thread overview]
Message-ID: <200702101732.13634.nakam@linux-ipv6.org> (raw)
In-Reply-To: <200702091522.35894.nakam@linux-ipv6.org>

Hi,

> > > >> > > What happens if a node (including a non-Linux one) receives a MH packet
> > > >> > > with a non-none next protocol? I might be wrong, but I would assume it
> > > >> > > parses it, at least in some cases.
> > >
> > > The node will send ICMP parameter problem back with code depending on
> > > whether the node supports MH or not.
> > > If it supports, the code is 0 (erroneous header field) as RFC3775.
> > > Otherwise, the code 1 (unrecognized Next Header).
> > >
> > >
> > > >> > > If this is trye, this patch might introduce a trivial way to evade
> > > >> > > firewall rules, as firewall admins will assume the next protocol is
> > > >> > > none, while it might not be.
> > > >> > >
> > > >> > > Of course, I could be plain wrong, since I do not know MH.
> > >
> > > If the sender creates MH with nexthdr=TCP for example,
> > > it may go through the firewall which is configured even MH=ACCEPT
> > > TCP=DROP. However, the receiver cannot handle it as TCP.
> > >
> > > Can I add nexthdr check, or should I rewrite it as "-m" module
> > > to treat MH as an extension header?
> > 
> > Personally, I'd prefer a check in the MH match that makes sure there is no 
> > more header, simply because we cannot assume that the sender keeps the 
> > rules.
> 
> Thanks for your comment.
> OK, I'll write additional patch to check no more header.
> 

Please find my patch (can be applied for net-2.6 tree) below.

Thanks,

-- 
Masahide NAKAMURA


From 457af7826fc1f3ae7e0c7b554b61a002e702a4cb Mon Sep 17 00:00:00 2001
From: Masahide NAKAMURA <nakam@linux-ipv6.org>
Date: Sat, 10 Feb 2007 14:46:05 +0900
Subject: [PATCH] [NETFILTER]: ip6_tables: Drop piggyback payload packet on MH.

Regarding RFC3775, MH payload proto field should be IPPROTO_NONE. Otherwise
it must be discarded (and the receiver should send ICMP error).

We assume filter should drop such piggyback everytime to disallow slipping through
firewall rules, even the final receiver will discard it.

Signed-off-by: Masahide NAKAMURA <nakam@linux-ipv6.org>
---
 net/ipv6/netfilter/ip6t_mh.c |    7 +++++++
 1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/net/ipv6/netfilter/ip6t_mh.c b/net/ipv6/netfilter/ip6t_mh.c
index 2c7efc6..c2a9098 100644
--- a/net/ipv6/netfilter/ip6t_mh.c
+++ b/net/ipv6/netfilter/ip6t_mh.c
@@ -66,6 +66,13 @@ match(const struct sk_buff *skb,
 		return 0;
 	}
 
+	if (mh->ip6mh_proto != IPPROTO_NONE) {
+		duprintf("Dropping invalid MH Payload Proto: %u\n",
+			 mh->ip6mh_proto);
+		*hotdrop = 1;
+		return 0;
+	}
+
 	return type_match(mhinfo->types[0], mhinfo->types[1], mh->ip6mh_type,
 			  !!(mhinfo->invflags & IP6T_MH_INV_TYPE));
 }
-- 
1.4.2

  reply	other threads:[~2007-02-10  8:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-26  9:53 [NETFILTER]: ip6_tables: Support MH match Yasuyuki KOZAKAI
2007-01-27 15:34 ` Rémi Denis-Courmont
     [not found]   ` <200701290507.l0T57mwf015698@toshiba.co.jp>
2007-01-30  4:23     ` Masahide NAKAMURA
2007-02-01  1:41   ` Yasuyuki KOZAKAI
2007-02-02 11:05     ` Jozsef Kadlecsik
2007-02-09  6:22       ` Masahide NAKAMURA
2007-02-10  8:32         ` Masahide NAKAMURA [this message]
2007-02-12 10:09           ` Patrick McHardy
     [not found] <200701260953.l0Q9rvV8006278@toshiba.co.jp>
2007-01-26 14:26 ` Patrick McHardy

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=200702101732.13634.nakam@linux-ipv6.org \
    --to=nakam@linux-ipv6.org \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=rdenis@simphalempin.com \
    --cc=usagi-core@linux-ipv6.org \
    --cc=yasuyuki.kozakai@toshiba.co.jp \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).