From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
---|---|
To: | Victor Wagner <vitus(at)wagner(dot)pp(dot)ru>, pgsql-hackers(at)postgresql(dot)org, Christoph Berg <myon(at)debian(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: OpenSSL 1.1 breaks configure and more |
Date: | 2016-07-05 13:46:53 |
Message-ID: | 34821a62-ac89-ffb2-7516-7a8b15c04723@proxel.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 07/05/2016 11:13 AM, Victor Wagner wrote:
> On Fri, 1 Jul 2016 02:27:03 +0200
> Andreas Karlsson <andreas(at)proxel(dot)se> wrote:
>> 0003-Remove-OpenSSL-1.1-deprecation-warnings.patch
>>
>> Silence all warnings. This commit changes more things and is not
>> necessary for getting PostgreSQL to build against 1.1.
>
> This patch breaks feature, which exists in PostgreSQL since 8.2 -
> support for SSL ciphers, provided by loadable modules such as Russian
> national standard (GOST) algorithms, and support for cryptographic
> hardware tokens (which are also supported by loadble modules called
> engines in OpenSSL).
>
> Call for OPENSSL_config was added to PostgreSQL for this purpose - it
> loads default OpenSSL configuration file, where such things as crypto
> hardware modules can be configured.
>
> If we wish to keep this functionality, we need to explicitely call
>
> OPENSSL_init_ssl(INIT_LOAD_CONFIG,NULL) instead of deprecated
> OPENSSL_config in 1.1.0
Thanks for testing the patches!
I have attached a new set of patches which this is fixed. I have also
skipped the last patch since OpenSSL has fixed the two issues I have
mentioned earlier in this thread.
Andreas
Attachment | Content-Type | Size |
---|---|---|
0001-Fixes-for-compiling-with-OpenSSL-1.1-v3.patch | text/x-patch | 14.5 KB |
0002-Remove-OpenSSL-1.1-deprecation-warnings-v3.patch | text/x-patch | 3.8 KB |
0003-Remove-px_get_pseudo_random_bytes-v3.patch | text/x-patch | 3.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2016-07-05 14:27:18 | Re: fixing subplan/subquery confusion |
Previous Message | Greg Stark | 2016-07-05 13:41:50 | can we optimize STACK_DEPTH_SLOP |