Re: Should we back-patch SSL renegotiation fixes?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Should we back-patch SSL renegotiation fixes?
Date: 2015-06-23 19:53:15
Message-ID: 7455.1435089195@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
>> On Tue, Jun 23, 2015 at 2:33 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> I do not know at this point whether these behaviors are really the same
>>> bug or not, but I wonder whether it's time to consider back-patching the
>>> renegotiation fixes we did in 9.4. Specifically, I think maybe we should
>>> back-patch 31cf1a1a4, 86029b31e, and 36a3be654.

> Yes, +1 for backpatching. Don't forget 5674460b and b1aebbb6.

Huh? 5674460b is ancient, and we concluded that b1aebbb6 didn't represent
anything much more than cosmetic fixes.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2015-06-23 19:57:52 Re: proposal: row_to_array function
Previous Message Alvaro Herrera 2015-06-23 19:49:08 Re: Should we back-patch SSL renegotiation fixes?