Re: _FORTIFY_SOURCE by default? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: _FORTIFY_SOURCE by default?
Date
Msg-id 29525.1347937826@sss.pgh.pa.us
Whole thread Raw
In response to Re: _FORTIFY_SOURCE by default?  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: _FORTIFY_SOURCE by default?  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> On Sun, 2012-09-16 at 15:58 -0400, Tom Lane wrote:
>> Maybe we're talking past each other.  What I thought you meant was
>> adding this #define unconditionally, without any awareness of what it
>> might do on particular platforms.  If you are thinking of adding it
>> only on platforms where it is considered standard, I can live with
>> that.

> I had suggested to put it into src/include/port/linux.h

OK, that's probably reasonable.

>> Another point to consider here is that (at least on Red Hat) I believe
>> this enables address-space randomization; which is something I very
>> much do not want to happen in debug builds.

> I doubt that a preprocessor symbol has anything to do with address-space
> randomization.  You are probably thinking of some other option that
> comes in with the hardening/security flags.

[ pokes around... ]  You're right, I was confusing this with
"_hardened_build".
        regards, tom lane



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: _FORTIFY_SOURCE by default?
Next
From: Craig Ringer
Date:
Subject: Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY