Re: controlling the location of server-side SSL files - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: controlling the location of server-side SSL files
Date
Msg-id 1330544176.30260.7.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: controlling the location of server-side SSL files  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: controlling the location of server-side SSL files  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On ons, 2012-02-29 at 14:27 -0500, Tom Lane wrote:
> Peter Eisentraut <peter_e@gmx.net> writes:
> > On ons, 2012-02-29 at 14:20 -0500, Tom Lane wrote:
> >> In particular, I observe that we get pushback anytime we break something
> >> in a way that makes SSL config files be required on the client side;
> >> see bug #6302 for most recent example.
> 
> > *If* we were to make a change in libpq analogous to the server side, the
> > effect would be to make the files less required, which could actually
> > help the case of bug #6302.
> 
> Hm?  Obviously I misunderstood what changes you were proposing to make,
> so would you mind spelling it out?

The details are to be determined, but a possible change would likely be
that instead of looking for a file and using it if and only if found,
there would be some kind of connection parameter saying "use this file
for this functionality", and otherwise it's not used.  The particular
example would be the CRL file.




pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: 16-bit page checksums for 9.2
Next
From: Andrew Dunstan
Date:
Subject: Re: "make check" in src/test/isolation is unworkable