Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:38522
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain chiaraquartet.net from 66.102.165.7 cause and error)
To: "Steph Fox" <steph@phparch.com>,"Marcus Boerger" <mail@marcus-boerger.de>
cc: "internals" <internals@lists.php.net>
Date: Sun, 22 Jun 2008 16:50:00 -0400
Mime-Version: 1.0
Importance: Normal
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Message-ID: <20080622215109.PNGU6859.atlmtaow02.cingularme.com@COM>
Subject: Re: OpenSSL and Phar
From: greg@chiaraquartet.net

Hi,

Steph, look more closely, the libraries are only used if openssl is built statically.  Otherwise, phar directly calls openssl_verify or openssl_sign.

Greg

-----Original Message-----

From:  "Steph Fox" <steph@phparch.com>
Subj:  OpenSSL and Phar
Date:  Sun Jun 22, 2008 4:32 pm
Size:  701 bytes
To:  "Greg Beaver" <greg@chiaraquartet.net>,"Marcus Boerger" <mail@marcus-boerger.de>
cc:  "internals" <internals@lists.php.net>


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