Re: Securing "make check" (CVE-2014-0067)

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Christoph Berg <cb(at)df7cb(dot)de>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: Securing "make check" (CVE-2014-0067)
Date: 2014-03-31 18:56:59
Message-ID: CA+TgmoYWbHY=PTgMjANfuUNy0jgWnvpGDGMUAf1SqUad-XnF=g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Mar 30, 2014 at 3:52 PM, Christoph Berg <cb(at)df7cb(dot)de> wrote:
> Re: Noah Misch 2014-03-30 <20140330014531(dot)GE170273(at)tornado(dot)leadboat(dot)com>
>> On Sat, Mar 29, 2014 at 10:04:55AM +0100, Christoph Berg wrote:
>> > Fwiw, to relocate the pg_regress socket dir, there is already the
>> > possibility to run make check EXTRA_REGRESS_OPTS="--host=/tmp". (With
>> > the pending fix I sent yesterday to extend this to contrib/test_decoding.)
>>
>> That doesn't work for "make check", because the postmaster ends up with
>> "listen_addresses=/tmp".
>
> Oh, right. There's this other patch which apparently works so well
> that I already forgot it's there:
>
> Enable pg_regress --host=/path/to/socket:
> https://alioth.debian.org/scm/loggerhead/pkg-postgresql/postgresql-9.4/trunk/view/head:/debian/patches/60-pg_regress_socketdir.patch

Wasn't this patch submitted for inclusion in PostgreSQL at some point?
Did we have some good reason for not accepting it?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Johnston 2014-03-31 18:59:19 Re: PQputCopyData dont signal error
Previous Message Robert Haas 2014-03-31 18:54:10 Re: issue log message to suggest VACUUM FULL if a table is nearly empty