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

Re: PQinitSSL broken in some use casesf

From: Andrew Chernow <ac(at)esilo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PQinitSSL broken in some use casesf
Date: 2009-03-30 15:24:01
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
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.

Andrew Chernow
eSilo, LLC
every bit counts

In response to


pgsql-hackers by date

Next:From: Emmanuel CecchetDate: 2009-03-30 15:42:53
Subject: Re: Partitioning feature ...
Previous:From: Andrew ChernowDate: 2009-03-30 15:07:55
Subject: Re: PQinitSSL broken in some use casesf

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