| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: openssl valgrind failures on skink are due to openssl issue |
| Date: | 2019-06-19 02:44:26 |
| Message-ID: | 20190619024426.rg4gnwvs7mhw4hwc@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-06-19 02:51:55 | Re: fix "Success" error messages |
| Previous Message | kuroda.hayato@fujitsu.com | 2019-06-19 02:43:56 | RE: [PATCH] memory leak in ecpglib |