Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 12 Apr 2003 00:38:36 -0700
From:      Kris Kennaway <kris@obsecurity.org>
To:        Mike Silbersack <silby@silby.com>
Cc:        Martin Blapp <mb@imp.ch>
Subject:   Re: fstack protector
Message-ID:  <20030412073836.GA86038@rot13.obsecurity.org>
In-Reply-To: <20030411115522.I6045@odysseus.silby.com>
References:  <20030411111302.G4749@cvs.imp.ch> <20030411115522.I6045@odysseus.silby.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--ReaqsoxgOBHFXBhH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Fri, Apr 11, 2003 at 11:58:02AM -0500, Mike Silbersack wrote:

> One possible solution would be to have a gcc-ssp port which would build a
> SSP version of the base system's compiler, and call it gcc-ssp or
> something.  Then we could make certain ports depend on using it, perhaps.

That's the best solution for FreeBSD.  You'd just set CC and CFLAGS if
you want to build with it, as usual.  Be aware that some ports will
not run when built with -fstack-protector, last time I checked
(XFree86 is one).

Kris

--ReaqsoxgOBHFXBhH
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+l8J7Wry0BWjoQKURAkcoAKDFUgNvqCXGfWqcS4y5TQzKXMro9ACeKudb
HIhM/NFyF7E0D6o6Kadq8fs=
=yXCh
-----END PGP SIGNATURE-----

--ReaqsoxgOBHFXBhH--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030412073836.GA86038>