Re: PQinitSSL broken in some use casesf - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PQinitSSL broken in some use casesf
Date
Msg-id 17415.1234554543@sss.pgh.pa.us
Whole thread Raw
In response to Re: PQinitSSL broken in some use casesf  (Andrew Chernow <ac@esilo.com>)
Responses Re: PQinitSSL broken in some use casesf
List pgsql-hackers
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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Chernow
Date:
Subject: Re: PQinitSSL broken in some use casesf
Next
From: Andrew Chernow
Date:
Subject: Re: PQinitSSL broken in some use casesf