From owner-freebsd-security Wed Feb 28 23:37:31 2001 Delivered-To: freebsd-security@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id E115837B71C; Wed, 28 Feb 2001 23:37:29 -0800 (PST) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W/smtpfeed 1.06) with ESMTP id QAA18007; Thu, 1 Mar 2001 16:37:29 +0900 (JST) To: Darren Reed , ume@mahoroba.org, Arjan.deVet@adv.iae.nl, n@nectar.com, freebsd@dohd.org, rasputin@FreeBSD-uk.eu.org, freebsd-security@freebsd.org, darrenr@freebsd.org In-reply-to: itojun's message of Thu, 01 Mar 2001 16:34:37 JST. <17940.983432077@coconut.itojun.org> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: IPFILTER IPv6 support non-functional? From: itojun@iijlab.net Date: Thu, 01 Mar 2001 16:37:29 +0900 Message-ID: <18005.983432249@coconut.itojun.org> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org to clarify, i'm not blaming anything. i am saying that: - there's a hard problem about packet filter language design and IPv6 intermediate headers. sys/netinet6/ip6_fw.c chases header chain, however, i'm not sure if it is totally right thing to do. - we need IPv6 filter code get tested with care. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message