Date: Fri, 1 Mar 2002 10:47:05 -0800 From: Luigi Rizzo <rizzo@icir.org> To: Leo Bicknell <bicknell@ufp.org> Cc: Bob Bishop <rb@gid.co.uk>, "George V. Neville-Neil" <gnn@neville-neil.com>, Doug Ambrisko <ambrisko@ambrisko.com>, hackers@FreeBSD.ORG Subject: Re: Multicast problem with sis interface? Message-ID: <20020301104705.A36640@iguana.icir.org> In-Reply-To: <20020301184123.GA5908@ussenterprise.ufp.org> References: <200203010557.VAA1802420@meer.meer.net> <rb@gid.co.uk> <4.3.2.7.2.20020222165515.00c14850@gid.co.uk> <200203010557.VAA1802420@meer.meer.net> <4.3.2.7.2.20020301112956.00c5b550@gid.co.uk> <20020301035623.A32974@iguana.icir.org> <20020301184123.GA5908@ussenterprise.ufp.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 01, 2002 at 01:41:23PM -0500, Leo Bicknell wrote: > In a message written on Fri, Mar 01, 2002 at 03:56:23AM -0800, Luigi Rizzo wrote: > > ok, these three drivers behave as follows: > > > > "ed" pads with whatever is left in the transmit buffer from > > earlier transmissions; > > "vr" pads with whatever is available in the mbuf after the actual data; > > I point out both of these are security risks. Granted, fairly I know, that is why i mentioned that. In fact i think i raised the subject long ago about this misbehaviour in some driver, maybe "dc". 0's or 1's are perfectly fine as padding, no need to put random stuff, especially given that from the header fields it is in most cases pretty obvious to find out what is the actual payload. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020301104705.A36640>