From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Removing SSL renegotiation (Was: Should we back-patch SSL renegotiation fixes?) |
Date: | 2015-06-24 15:15:42 |
Message-ID: | 20150624151542.GU4797@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2015-06-24 11:11:16 -0400, Tom Lane wrote:
> On balance I think I agree that SSL renegotiation has not been worth the
> trouble. And we definitely aren't testing it adequately, so if we wanted
> to keep it then there's even *more* work that somebody ought to expend.
Right. Our code was nearly entirely broken for streaming replication for
*years* without anybody noticing. And even now it doesn't reliably
work. It's also pretty hard to test due to the required data volumes and
the vast number of different behaviours across openssl versions.
> I assume we'd back-patch it, too? (Probably not remove the
> ssl_renegotiation_limit variable, but always act as though it were
> zero.)
Yes, I think so. Maybe log a warning at startup if set to nonzero
(startup is probably the best we can do).
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2015-06-24 15:30:47 | Re: Multixid hindsight design |
Previous Message | Tom Lane | 2015-06-24 15:11:16 | Re: Removing SSL renegotiation (Was: Should we back-patch SSL renegotiation fixes?) |