| From: | Dave Page <dpage(at)postgresql(dot)org> |
|---|---|
| To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: OpenSSL Applink |
| Date: | 2007-09-28 16:09:24 |
| Message-ID: | 46FD2734.8070303@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Heikki Linnakangas wrote:
> Dave Page wrote:
>> Andrew Dunstan wrote:
>>> Dave Page wrote:
>>>> I believe we just didn't notice it until now because the older Mingw
>>>> builds use the MSVC 6.0 runtimes which just happened to be compatible
>>>> with the OpenSSL binary builds (we're now using 8.0), in addition to
>>>> which there are relatively few people using client-side certs I'd wager.
>>> So SSL works without this wart if you don't have a client cert?
>> Yep.
>
> According to the OpenSSL FAQ, the purpose of the applink is to allow
> mixing release and debug versions or multi-threaded and
> non-multithreaded versions of libraries:
>
> http://www.openssl.org/support/faq.html#PROG2
Yeah - which in itself is a pita because with their 'workaround' we now
need to ensure we use a debug libpq with a debug pgadmin whereas
previously mixing 'n' matching wasn't an issue.
> How come we only bump into the crash with client certs?
>
I assume it uses fopen() or one of the other functions it does a
GetProcAddress() on in that situation.
/D
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-09-28 16:13:32 | Re: OpenSSL Applink |
| Previous Message | Heikki Linnakangas | 2007-09-28 15:50:17 | Re: OpenSSL Applink |