Horton
Menu

Re: Recent vendor SSL renegotiation patches break PostgreSQL

Dave Page <dpage@pgadmin.org>

View thread
From: Dave Page <dpage@pgadmin.org>
To: jd@commandprompt.com
Cc: Magnus Hagander <magnus@hagander.net>, Tom Lane <tgl@sss.pgh.pa.us>, Bruce Momjian <bruce@momjian.us>, Chris Campbell <chris_campbell@mac.com>, Robert Haas <robertmhaas@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2010-02-22T19:00:20Z
Lists: pgsql-hackers 
On 2/22/10, Joshua D. Drake <jd@commandprompt.com> wrote:
> On Mon, 2010-02-22 at 18:45 +0100, Magnus Hagander wrote:
>> 2010/2/22 Joshua D. Drake <jd@commandprompt.com>:
>> > On Mon, 22 Feb 2010 18:00:33 +0100, Magnus Hagander
>> > <magnus@hagander.net>
>> > wrote:
>> >
>> >> We also have to consider our Windows users, where *we* ship the
>> >> OpenSSL library. Where there is no library we can ship right now that
>> >> fixes it.
>> >
>> > We do? I mean I know that we provide the old 8.2/8.3 pginstaller, but
>> > EDB
>> > is the provider of w32 binaries, not the community.
>>
>> How does that change the fact even a tiny bit for the end user?
>
> Only that EDB may chose to put in there own

We're certainly not going to be shipping anything but standard
PostgreSQL, and i don't have the cycles or energy to try building
bespoke versions of openssl.