From mboxrd@z Thu Jan 1 00:00:00 1970 From: Evgeniy Polyakov Subject: Re: Passive OS fingerprint xtables match. Date: Fri, 13 Feb 2009 17:22:04 +0300 Message-ID: <20090213142204.GA27554@ioremap.net> References: <20090212171245.GA15025@ioremap.net> <20090212185729.GA17896@ioremap.net> <20090213130347.GD23879@ioremap.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Patrick McHardy , netdev@vger.kernel.org, David Miller , "Paul E. McKenney" , Netfilter Development Mailinglist To: Jan Engelhardt Return-path: Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-Id: netfilter-devel.vger.kernel.org On Fri, Feb 13, 2009 at 02:51:48PM +0100, Jan Engelhardt (jengelh@medozas.de) wrote: > >> config NETFILTER_XT_MATCH_COMMENT > >> tristate '"comment" match support' > >> depends on NETFILTER_ADVANCED > >> ---help--- > > > >But I placed OSF into net/ipv4/netfilter/ipt_osf.c, should it be moved > >into different location? > > That would be preferable -> net/netfilter/xt_osf.c. Ok, I will move it there. > >> >proper offset (modulo of the option size). > >> > >> What if optp is odd? > > > >It cant, header is fixed and every option length is also fixed (and its > >size is checked). > > This RFC-compliant ("An option may begin on any octet boundary.") > option byte stream seems to produce an odd optp value: > > 01 02 04 05 a0 00 > > or where did I go wrong? OSF checks only MSS and timestamp options. -- Evgeniy Polyakov