Re: openssl valgrind failures on skink are due to openssl issue - Mailing list pgsql-hackers

From Andres Freund
Subject Re: openssl valgrind failures on skink are due to openssl issue
Date
Msg-id 20190619024426.rg4gnwvs7mhw4hwc@alap3.anarazel.de
Whole thread Raw
In response to Re: openssl valgrind failures on skink are due to openssl issue  (Michael Paquier <michael@paquier.xyz>)
Responses Re: openssl valgrind failures on skink are due to openssl issue
List pgsql-hackers
On 2019-06-19 11:28:16 +0900, Michael Paquier wrote:
> On Tue, Jun 18, 2019 at 04:34:07PM -0700, Andres Freund wrote:
> > It's merged to both branches that contain the broken code. Now we need
> > to wait for the next set of openssl releases, and then for distros to
> > pick that up. Based on the past release cadence
> > https://www.openssl.org/news/openssl-1.1.1-notes.html
> > that seems to be likely to happen within 2-3 months.
> 
> If that's for the buildfarm coverage.  I would be of the opinion to
> wait a bit.

Yea. For now I've just disabled ssl support on skink, but that has its
own disadvantages.

> Another possibility is that you could compile your own
> version of OpenSSL with the patch included, say only 1.1.1c with the
> patch.

Really, I can do that?



pgsql-hackers by date:

Previous
From: "kuroda.hayato@fujitsu.com"
Date:
Subject: RE: [PATCH] memory leak in ecpglib
Next
From: Michael Paquier
Date:
Subject: Re: fix "Success" error messages