Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:38517
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain phparch.com from 64.99.136.147 cause and error)
Message-ID: <028a01c8d4a7$18dd4380$4401a8c0@foxbox>
Reply-To: "Steph Fox" <steph@phparch.com>
To: "Greg Beaver" <greg@chiaraquartet.net>,
	"Marcus Boerger" <mail@marcus-boerger.de>
Cc: "internals" <internals@lists.php.net>
Date: Sun, 22 Jun 2008 21:32:30 +0100
Organization: php|architect
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="UTF-8";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: OpenSSL and Phar
From: steph@phparch.com ("Steph Fox")


Hi Greg, all,

It seems we don't use the openssl extension API at all in ext/phar, just the 
actual OpenSSL headers and libs. That means Phar with OpenSSL support can be 
both built and run without ext/openssl being built at all, but requires 
third-party libs (under Windows at least - ssleay32.dll and libeay32.dll) in 
the same way that ext/openssl does.

I'm wondering if we shouldn't have a separate configuration option for 
this - something like --enable-phar-ssl - rather than testing 
for --with-openssl in the config line.

The chief advantage of this approach is that it doesn't matter whether 
phar-ssl is built as shared or not, since the dependency is outside PHP.

Thoughts?

- Steph