Re: OpenSSL 1.1 breaks configure and more

From: Andreas Karlsson <andreas(at)proxel(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christoph Berg <myon(at)debian(dot)org>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: OpenSSL 1.1 breaks configure and more
Date: 2016-07-01 00:27:03
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


Here is an initial set of patches related to OpenSSL 1.1. Everything
should still build fine on older OpenSSL versions (and did when I tested
with 1.0.2h).


This patch fixes the code so it builds with OpenSSL 1.1 (except the
CRYPTO_LOCK issue I have reported to the OpenSSL team).

- Makes our configure script check for SSL_new instead
- Uses functions instead of direct access to struct members


Fix for the removal of the CRYPTO_LOCK define. I am trying to convince
them to add the define back. :)


Silence all warnings. This commit changes more things and is not
necessary for getting PostgreSQL to build against 1.1.

- Silences deprecation other warnings related to that OpenSSL 1.1 now
1) automatically initializes the library and 2) no longer uses the
locking callback.
- Silences deprecation warning when generating DH parameters.


Attachment Content-Type Size
0001-Fixes-for-compiling-with-OpenSSL-1.1.patch text/x-patch 10.3 KB
0002-Define-CRYPTO_LOCK-for-OpenSSL-1.1-compat.patch text/x-patch 824 bytes
0003-Remove-OpenSSL-1.1-deprecation-warnings.patch text/x-patch 3.7 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tsunakawa, Takayuki 2016-07-01 00:33:11 Is a UDF binary portable across different minor releases and PostgreSQL distributions?
Previous Message Marko Tiikkaja 2016-07-01 00:12:56 Allow INSTEAD OF DELETE triggers to modify the tuple for RETURNING