Re: src/test/ssl broken on HEAD - Mailing list pgsql-hackers

From Andres Freund
Subject Re: src/test/ssl broken on HEAD
Date
Msg-id 20150902231547.GG8555@awork2.anarazel.de
Whole thread Raw
In response to Re: src/test/ssl broken on HEAD  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: src/test/ssl broken on HEAD  (Noah Misch <noah@leadboat.com>)
Re: src/test/ssl broken on HEAD  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On 2015-09-02 17:03:46 -0400, Robert Haas wrote:
> On Wed, Sep 2, 2015 at 4:50 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
> > Tell me what's needed and I'll look at creating a buildfarm test module for
> > it.
> 
> You run the tests via: make -C src/test/ssl check
> 
> But nota bene security caveats:
> 
> commit e39250c644ea7cd3904e4e24570db21a209cf97f
> Author: Heikki Linnakangas <heikki.linnakangas@iki.fi>
> Date:   Tue Dec 9 17:21:18 2014 +0200
> 
>     Add a regression test suite for SSL support.
> 
>     It's not run by the global "check" or "installcheck" targets, because the
>     temporary installation it creates accepts TCP connections from any user
>     the same host, which is insecure.

We could just implement SSL over unix sockets. Obviously the
connection-encryption aspect isn't actually useful, but e.g. client
certs still make sense.  Besides, it allows to avoid concerns like the
above...

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: DBT-3 with SF=20 got failed
Next
From: Peter Geoghegan
Date:
Subject: Re: Memory prefetching while sequentially fetching from SortTuple array, tuplestore