From owner-freebsd-security Thu Nov 16 17: 8:40 2000 Delivered-To: freebsd-security@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id ADD4A37B479; Thu, 16 Nov 2000 17:08:37 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAH18aQ02980; Thu, 16 Nov 2000 18:08:36 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA70664; Thu, 16 Nov 2000 18:08:35 -0700 (MST) Message-Id: <200011170108.SAA70664@harmony.village.org> To: Kris Kennaway Subject: Re: FYI: Propolice for gcc-2.95.2 Cc: Mike Silbersack , KOJIMA Hajime , security@FreeBSD.ORG In-reply-to: Your message of "Thu, 16 Nov 2000 17:00:42 PST." <20001116170042.A58481@citusc17.usc.edu> References: <20001116170042.A58481@citusc17.usc.edu> <200011162332.QAA69958@harmony.village.org> Date: Thu, 16 Nov 2000 18:08:35 -0700 From: Warner Losh Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20001116170042.A58481@citusc17.usc.edu> Kris Kennaway writes: : > I'd worry about putting this into the base system. First, I'd worry : > about the performance impact of all this extra code in the base : > system. Second, I'd worry about bitrot when we move to new versions : > of the source. : : Performance shouldn't be an issue unless you enable the extra bounds : checking at compile time. Right. I guess I'd worry about this being enabled by default as a way of "solving" all stack smashing problems. If it is just a knob to enable for those that want to enable it, I'd be cool with that. : Bitrot is certainly an issue, though. We should at least allow world : to be built using a propolice-enabled compiler - though that should be : fairly automatic just using CC and CFLAGS. My concern would be if we put this into the 2.95.2 tree that we have. I'd have no problems with making this "easy" to enable. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message