Re: Should we back-patch SSL renegotiation fixes?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Should we back-patch SSL renegotiation fixes?
Date: 2015-06-24 21:08:56
Message-ID: CA+Tgmobi92_5_fepjhPC+wHVfXGY5_Ckz7PCdwrKg0bjz3+h_w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 24, 2015 at 3:41 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On 6/24/15 3:13 PM, Andres Freund wrote:
>> Meh. The relevant branches already exist, as you can disable it today.
>>
>> We could also just change the default in the back branches.
>
> One more argument for leaving everything alone. If users don't like it,
> they can turn it off themselves.

I find it very hard to disagree with that perspective.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-06-24 21:20:31 Re: Should we back-patch SSL renegotiation fixes?
Previous Message Josh Berkus 2015-06-24 20:22:41 Re: pgbench - allow backslash-continuations in custom scripts