From owner-freebsd-net Sun Dec 30 10: 1:30 2001 Delivered-To: freebsd-net@freebsd.org Received: from niwun.pair.com (niwun.pair.com [209.68.2.70]) by hub.freebsd.org (Postfix) with SMTP id BFC9337B416 for ; Sun, 30 Dec 2001 10:01:25 -0800 (PST) Received: (qmail 34406 invoked by uid 3193); 30 Dec 2001 18:01:25 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 Dec 2001 18:01:25 -0000 Date: Sun, 30 Dec 2001 13:01:24 -0500 (EST) From: Mike Silbersack X-Sender: To: Randall Stewart Cc: Bosko Milekic , Subject: Re: m_reclaim and a protocol drain In-Reply-To: <3C2F0D40.ADFE2B6F@stewart.chicago.il.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 30 Dec 2001, Randall Stewart wrote: > > Heh, you nailed the reverse of the problem we've seen: Right now the easy > > way to cause exhaustion is to fill up _send_ buffers, via netkill. I > > guess if we solve that problem, out of order segments could be used for an > > attack too. > > > > Mike: > > Interesting problem.. but I was thinking in terms of > a outside attacker.. not someone who has a login id on > your machine. That leads down another path... i.e. local > machine security. > > > R Heh, you don't have to be local to cause a machine to send you something. Just find a service which exists to send data (http, pop3, ftp, irc), and you're in business. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message