Re: PostgreSQL12 and older versions of OpenSSL

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Victor Wagner <vitus(at)wagner(dot)pp(dot)ru>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: PostgreSQL12 and older versions of OpenSSL
Date: 2019-09-26 06:56:46
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Thu, Sep 26, 2019 at 02:03:12AM -0400, Tom Lane wrote:
> What I'm concerned about at the moment is Peter's comment upthread
> that what we seem to be dealing with here is a broken vendor patch,
> not any officially-released OpenSSL version at all. Is it our job
> to work around that situation, rather than pushing the vendor to
> fix their patch?

Yes, rather broken. SUSE got the header visibly right, at least the
version string is not. The best solution in our favor would be that
they actually fix their stuff :)

And OpenSSL is also to blame by not handling those flags consistently
in a stable branch..

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-09-26 07:00:12 Re: Bloom index cost model seems to be wrong
Previous Message Michael Paquier 2019-09-26 06:52:03 Re: Cache lookup errors with functions manipulation object addresses