Skip site navigation (1) Skip section navigation (2)

Re: PQinitSSL broken in some use casesf

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Andrew Chernow <ac(at)esilo(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PQinitSSL broken in some use casesf
Date: 2009-03-30 17:44:13
Message-ID: 49D104ED.6010008@hagander.net (view raw or flat)
Thread:
Lists: pgsql-hackers
Bruce Momjian wrote:
> Magnus Hagander wrote:
>> On 30 mar 2009, at 17.24, Andrew Chernow <ac(at)esilo(dot)com> wrote:
>>
>>> Tom Lane wrote:
>>>> BTW, unless someone objects I'd like to make the name of that  
>>>> function
>>>> PQinitSecurity.
>>> Agreed.  Although, both PQinitSecure and PQinitSecurity are very  
>>> general names.  "Security" can mean a lot of things.  Maybe the name  
>>> should be more particular, like PQinitOpenSSL.  I think its okay to  
>>> reference the openssl project name being how this function is  
>>> designed to work with openssl's library split.
>>>
>> +1
>>
>> It's quite likely that well want to support another ssl library in the  
>> future. At least likely enough that any api we define should take it  
>> into consideration.
> 
> Are we sure we don't want to add a more general libpq initialization
> control at this time?
> 
> 	PQinitOptions(PG_NO_SSL_INIT | PG_NO_CRYPTO_INIT);

Could be an option but if we go down that path, it needs to be
PG_NO_OPENSSL_SSL_INIT and PG_NO_OPENSSL_CRYPTO_INIT....

//Magnus


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-03-30 17:44:44
Subject: Re: More message encoding woes
Previous:From: Bruce MomjianDate: 2009-03-30 17:40:14
Subject: Re: PQinitSSL broken in some use casesf

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group