pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Victor Wagner <vitus@wagner.pp.ru>
To: pgsql-hackers@postgresql.org
Subject: Re: OpenSSL 1.1 breaks configure and more
Date: Tue, 5 Jul 2016 12:13:47 +0300
Message-ID: <20160705121347.5c5c702f@fafnir.local.vm> (raw)
In-Reply-To: <688a438c-ccc2-0431-7100-26e418fc3bca@proxel.se>
References: <20160627151604.GD1051@msg.df7cb.de>
	<1805.1467041061@sss.pgh.pa.us>
	<8a0a5959-0b83-3dc8-d9e7-66ce8c1c5bc7@proxel.se>
	<688a438c-ccc2-0431-7100-26e418fc3bca@proxel.se>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On Fri, 1 Jul 2016 02:27:03 +0200
Andreas Karlsson <andreas@proxel.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








-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (57+ messages)  latest in thread

Message-ID: <20160705121347.5c5c702f@fafnir.local.vm>
Permalink:  ../20160705121347.5c5c702f@fafnir.local.vm/
Also on:    postgresql.org/message-id/20160705121347.5c5c702f@fafnir.local.vm

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: vitus@wagner.pp.ru
  Subject: Re: OpenSSL 1.1 breaks configure and more
  In-Reply-To: <20160705121347.5c5c702f@fafnir.local.vm>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox