Re: Re: PHP 7.0 and openssl 1.1

From: Date: Mon, 23 Jan 2017 22:36:58 +0000
Subject: Re: Re: PHP 7.0 and openssl 1.1
References: 1 2 3 4 5 6  Groups: php.internals 
Request: Send a blank email to internals+get-97941@lists.php.net to get a copy of this message
On Mon, Jan 23, 2017 at 12:52 PM, Alice Wonder <alice@librelamp.com> wrote: > Actually I found that wasn't the case. To build php against an alternat > openssl API - I did have to rebuild net-snmp but curl, for example, at > least on CentOS uses NSS for it's TLS and so didn't need to be rebuild to > build PHP against a different OpenSSL API. > > Building in mock, the only php dependency that had an OpenSSL API > dependency was net-snmp. And if I kept the same API for net-snmp, I didn't > have to replace the system net-snmp for php to work properly - only the > net-snmp used in mock. > > Well, you got lucky with your libcurl then. On Debian the default is openssl. You can optionally choose either gnutls or nss instead if you like. I am pretty sure Centos also has a libcurl-openssl variant that people might be using: libcurl3 - easy-to-use client-side URL transfer library (OpenSSL flavour) libcurl3-gnutls - easy-to-use client-side URL transfer library (GnuTLS flavour) libcurl3-nss - easy-to-use client-side URL transfer library (NSS flavour) libcurl having those alternatives is probably the easiest dependency. libpq (PostgreSQL) and libc-client do not, as far as I know. -Rasmus

« previous php.internals (#97941) next »