From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
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:40:14 |
Message-ID: | 200903301740.n2UHeEM29830@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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);
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2009-03-30 17:44:13 | Re: PQinitSSL broken in some use casesf |
Previous Message | Tom Lane | 2009-03-30 17:31:23 | Re: Unexpected Result in Windowing |