Re: Recent vendor SSL renegotiation patches break PostgreSQL

From: Dave Page <dpage(at)pgadmin(dot)org>
To: jd(at)commandprompt(dot)com
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Chris Campbell <chris_campbell(at)mac(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Recent vendor SSL renegotiation patches break PostgreSQL
Date: 2010-02-22 19:00:20
Message-ID: 937d27e11002221100k1743ff3bq10bc51cb09c2bb29@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2/22/10, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> On Mon, 2010-02-22 at 18:45 +0100, Magnus Hagander wrote:
>> 2010/2/22 Joshua D. Drake <jd(at)commandprompt(dot)com>:
>> > On Mon, 22 Feb 2010 18:00:33 +0100, Magnus Hagander
>> > <magnus(at)hagander(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2010-02-22 19:00:50 Re: What does this configure warning mean?
Previous Message Jaime Casanova 2010-02-22 18:59:43 Re: tie user processes to postmaster was:(Re: [HACKERS] scheduler in core)