From owner-freebsd-security Fri Jan 21 8:41:22 2000 Delivered-To: freebsd-security@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id BCDD8154E0 for ; Fri, 21 Jan 2000 08:41:19 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com ident=wes) by mail.xmission.com with esmtp (Exim 3.03 #3) id 12Bh7a-0001ZG-00; Fri, 21 Jan 2000 09:41:14 -0700 Message-ID: <38888D31.CFF5CF38@softweyr.com> Date: Fri, 21 Jan 2000 09:45:37 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Brett Glass Cc: Alfred Perlstein , Matthew Dillon , security@FreeBSD.ORG Subject: Re: stream.c worst-case kernel paths References: <4.2.2.20000120222630.01919150@localhost> <4.2.2.20000120182425.01886ec0@localhost> <20000120195257.G14030@fw.wintelcom.net> <4.2.2.20000120220649.018faa80@localhost> <200001210521.VAA56412@apollo.backplane.com> <4.2.2.20000120222630.01919150@localhost> <4.2.2.20000121081444.01a2d480@localhost> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brett Glass wrote: > > So, we've learned something about what policy to follow. The current TCP/IP > spec is an important standard, but it's not Holy Writ. There are still > things we can learn, and we can fix both the current spec and future ones. > > Whether we implement changes immediately or not is really a matter of > pragmatism. My priority is to keep my systems up and safe from attack, so > I have no qualms about doing that so long as it won't break normal operation. > I'd put in a "stick to the original spec" option for those who were willing > to risk safety for conformance to Holy Writ. YMMV, of course. Nobody disagrees with this; that's why we ALL use systems with source code available. The only argument is whether the defensive posture should be the default or not. Following the specifications as written should be the default setting; we can still use studies of the defensive posture to convince the IETF of the value of changes to the protocol. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message