| From: | Andrew Chernow <ac(at)esilo(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, 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-10 17:05:20 |
| Message-ID: | 4991B3D0.7020604@esilo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
> Andrew Chernow wrote:
>> Tom Lane wrote:
>>> If that's all you want, then PQinitSSLExtended is a perfectly good
>>> answer.
>>>
>> How about PQinitCrypto(bool do_init), which would default to TRUE if
>> never called. PQinitSSL already handles the SSL part, just need control
>> over initializing crypto.
>
> Folks, we need a lot more demand before we add functions to libpq.
>
Honestly, I'm not suggesting that a function is added. If others decide
to do that, I think the function's purpose should be to init crypto. We
don't need another way to init ssl.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2009-02-10 17:05:50 | Re: PQinitSSL broken in some use casesf |
| Previous Message | Dave Page | 2009-02-10 17:03:34 | Re: PQinitSSL broken in some use casesf |