Date: Mon, 9 Aug 1999 21:34:49 +0200 From: Marc Olzheim <marcolz@stack.nl> To: Greg Lynn <dglynn@vaview5.vavu.vt.edu> Cc: Marc Olzheim <marcolz@stack.nl>, freebsd-stable@freebsd.org Subject: Re: testsockbuf.c Message-ID: <19990809213449.A5585@stack.nl> In-Reply-To: <Pine.BSF.3.96.990809152359.1209A-100000@vaview5.vavu.vt.edu>; from Greg Lynn on Mon, Aug 09, 1999 at 03:26:24PM -0400 References: <19990809212324.A4984@stack.nl> <Pine.BSF.3.96.990809152359.1209A-100000@vaview5.vavu.vt.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> Isn't this a huge problem for ordinary users on a system?? I mean > there aren't any user restrictions on sockets right? I imagine > there will be some sort of follow up on this exploit? Well, there is a 256k limit per socket of the buffer (I & O), try sysctl kern.maxsockbuf and you can limit the number of sockets with the maximum number of filedescriptors per process (ulimit -a), but that's just not safe enough. It seems that the kernel doesn't check wether the space it wants to allocate still exists or not. Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990809213449.A5585>