Re: _FORTIFY_SOURCE by default?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: _FORTIFY_SOURCE by default?
Date: 2012-09-18 03:10:26
Message-ID: 29525.1347937826@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2012-09-18 07:07:05 Re: WIP patch: add (PRE|POST)PROCESSOR options to COPY
Previous Message Peter Eisentraut 2012-09-18 02:50:27 Re: _FORTIFY_SOURCE by default?