Re: PQinitSSL broken in some use casesf

Tom Lane wrote:
> Andrew Chernow <ac@esilo.com> writes:
>>> Also, this definition feels a bit wrong --- it's not possible for
>>> all four cases to be valid, is it?
> 
>> Yes it is.
> 
>> PQinitSSLExtended(0, 0); // don't init anything, PQinitSSL(0)
>> PQinitSSLExtended(1, 0); // init ssl, don't init crypto
>> PQinitSSLExtended(0, 1); // don't init ssl, init crypto
>> PQinitSSLExtended(1, 1); // init both, default behavior, PQinitSSL(1)
> 
> I know what you're thinking the flags should mean, I'm saying that it's
> not possible for the third case to be sane.  It implies that the
> application initialized ssl but not crypto, which isn't possible.
> 

Or that the application called PQinitSSLExtended(0, 1) and then 
initialized SSL itself, which is sane.

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