From owner-freebsd-security Mon Aug 16 18:25:10 1999 Delivered-To: freebsd-security@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 1683C1546F for ; Mon, 16 Aug 1999 18:25:07 -0700 (PDT) (envelope-from mike@sentex.net) Received: from gravel (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id VAA25174; Mon, 16 Aug 1999 21:24:31 -0400 (EDT) Message-Id: <4.1.19990816213403.05a3b540@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 16 Aug 1999 21:37:32 -0400 To: Matthew Dillon From: Mike Tancsa Subject: Re: Any work around for this FreeBSD bug/DoS ? Cc: freebsd-security@FreeBSD.ORG In-Reply-To: <199908170119.SAA12524@apollo.backplane.com> References: <4.1.19990816203409.05989960@granite.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Try adjusting the kern.ipc.maxsockbuf sysctl. Thanks for the quick response Matt. But to what value, and what are the implications / trade offs ? Sorry, was this discussed before somewhere ? I didnt see any followup in stable where I originally saw it posted. Doing a search in Dejanews through the mailing lists, I only see three old references to this particular param from 6 months ago. ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message