| From: | Andrew Chernow <ac(at)esilo(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | 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-02-11 00:49:00 |
| Message-ID: | 4992207C.7060707@esilo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Tue, Feb 10, 2009 at 5:02 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> PQinitSSL(false) initializes crypto? Please point me to exact function
>> calls that are the problem? Everything is very vague.
File: src/interfaces/libpq/fe-secure.c
Func: init_ssl_system
Line: 823
Starting at around line 853, this function prepares a lock array for
CRYPTO_set_locking_callback. This function is not part of libssl, its
part of libcrypto. It also calls CRYPTO_set_id_callback. The rest of
that function appears to only make libssl calls.
There should be an "if (pq_initcryptolib)" around those libcrypto calls,
serving the same purpose as the pq_initssllib variable.
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonah H. Harris | 2009-02-11 01:09:03 | Re: Optimization rules for semi and anti joins |
| Previous Message | David Rowley | 2009-02-10 22:41:37 | Re: Bug #4284 |