Date: Wed, 1 Sep 1999 21:14:53 -0400 (EDT) From: Bill Fumerola <billf@jade.chc-chimes.com> To: Don Lewis <Don.Lewis@tsc.tdk.com> Cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, Nick Hibma <hibma@skylink.it>, FreeBSD -- The Power to Serve <geniusj@free-bsd.org>, Mike Tancsa <mike@sentex.net>, freebsd-security@FreeBSD.ORG Subject: Re: FW: Local DoS in FreeBSD Message-ID: <Pine.BSF.4.10.9909012111180.66968-100000@jade.chc-chimes.com> In-Reply-To: <199909020205.TAA08666@salsa.gv.tsc.tdk.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 1 Sep 1999, Don Lewis wrote:
> It should be possible to track the overall socket buffer space for each
> UID, but how do you enforce the limit? Do you cause the socket(),
> socketpair(), accept(), and setsockopt() calls to fail? Will userland
> code react well to this?
Any good code uses errx() or one of it's cousins.
53 ECONNABORTED Software caused connection abort. A connection abort was
caused internal to your host machine.
looks like a good thing to return when that is the case.
--
- bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp -
- ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org -
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9909012111180.66968-100000>