Re: Should we back-patch SSL renegotiation fixes?

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

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Fri, Jun 26, 2015 at 9:59 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> Generally I'd agree that that is a bad thing. But there's really not
>> much of a observable behaviour change in this case? Except that
>> connections using ssl break less often.

> Well, SSL renegotiation exists for a reason: to improve security.

That was the theory, yes, but the CVEs that have come out of it indicate
that whether it improves security *in practice* is a pretty debatable
topic. The fact that the new TLS draft drops it altogether tells us
something about the conclusion the standards community has arrived at.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-06-26 14:33:48 Re: Should we back-patch SSL renegotiation fixes?
Previous Message Robert Haas 2015-06-26 14:26:58 Re: Should we back-patch SSL renegotiation fixes?