Re: PQinitSSL broken in some use casesf

From: Andrew Chernow <ac(at)esilo(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PQinitSSL broken in some use casesf
Date: 2009-02-11 14:15:02
Message-ID: 4992DD66.4020503@esilo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas wrote:
> On Feb 11, 2009, at 12:12 AM, Andrew Chernow <ac(at)esilo(dot)com> wrote:
>
>> Robert Haas wrote:
>>> I am not in love with the idea of using PQinitSSL(SOME_MAGIC_VALUE)
>>
>> The issue I see is the inability to toggle crypto initialization. I
>> think crypto init and ssl init are 2 different things. Thus, I
>> proposed the below:
>>
>> http://archives.postgresql.org/pgsql-hackers/2009-02/msg00488.php
>
> If that can be made transparent to existing apps, I'm all for it.
>

Defaulting the crypto initialization to TRUE should make this
transparent. The downside is that this breaks backwards compatibility,
since an unknown symbol is being referenced. Although, that only occurs
when PQinitCrypto is actually used.

--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonah H. Harris 2009-02-11 14:36:38 Re: Optimization rules for semi and anti joins
Previous Message Peter Eisentraut 2009-02-11 14:06:31 Re: So, what locale should the regression tests run in?