From owner-freebsd-security Wed Nov 3 8:29:51 1999 Delivered-To: freebsd-security@freebsd.org Received: from phoenix.aye.net (phoenix.aye.net [206.185.8.134]) by hub.freebsd.org (Postfix) with SMTP id 3268C1506B for ; Wed, 3 Nov 1999 08:29:48 -0800 (PST) (envelope-from barrett@phoenix.aye.net) Received: (qmail 27775 invoked by uid 1000); 3 Nov 1999 16:30:04 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 3 Nov 1999 16:30:04 -0000 Date: Wed, 3 Nov 1999 11:30:04 -0500 (EST) From: Barrett Richardson To: David G Andersen Cc: Andre Gironda , frank@hellbell.agava.ru, freebsd-security@FreeBSD.ORG Subject: Re: stack protecting In-Reply-To: <199911031358.GAA22340@faith.cs.utah.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 3 Nov 1999, David G Andersen wrote: > Lo and behold, Andre Gironda once said: > > > > > > Stack protection doesn't work as there are still heap overflows and > > race conditions. it's best to apply TPE patches (Phrack, Issue 52/54), > > like originally implemented on upt.org. Or write perfect code ;> > > While I agree with you that it's not a perfect solution, isn't that > like saying that using a car alarm isn't a good idea, even though it will > prevent 50% of the breakins to your car? > > Defense in depth *is* a good idea. Stackguard and like products can > help quite a bit with this. > > Now, given that, Stackguard doesn't support FreeBSD. :) > > -Dave > Takes some minor twiddleing. What it upt.org? It doesn't resolve. - Barrett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message