Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:38527 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 66096 invoked from network); 23 Jun 2008 03:32:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jun 2008 03:32:27 -0000 Authentication-Results: pb1.pair.com smtp.mail=greg@chiaraquartet.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=greg@chiaraquartet.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain chiaraquartet.net from 38.99.98.18 cause and error) X-PHP-List-Original-Sender: greg@chiaraquartet.net X-Host-Fingerprint: 38.99.98.18 beast.bluga.net Linux 2.6 Received: from [38.99.98.18] ([38.99.98.18:36893] helo=mail.bluga.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3F/5C-23032-9491F584 for ; Sun, 22 Jun 2008 23:32:26 -0400 Received: from mail.bluga.net (localhost.localdomain [127.0.0.1]) by mail.bluga.net (Postfix) with ESMTP id 5D3ADC130E7; Sun, 22 Jun 2008 20:32:30 -0700 (MST) Received: from [192.168.1.101] (static-66-14-247-16.bdsl.verizon.net [66.14.247.16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bluga.net (Postfix) with ESMTP id 79E6AC130BF; Sun, 22 Jun 2008 20:32:29 -0700 (MST) Message-ID: <485F1940.3050504@chiaraquartet.net> Date: Sun, 22 Jun 2008 22:32:16 -0500 User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Pierre Joye CC: Steph Fox , Marcus Boerger , internals References: <20080622215109.PNGU6859.atlmtaow02.cingularme.com@COM> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: [PHP-DEV] Re: OpenSSL and Phar From: greg@chiaraquartet.net (Greg Beaver) Pierre Joye wrote: > hi Greg, > > On Sun, Jun 22, 2008 at 10:50 PM, wrote: > >> Hi, >> >> Steph, look more closely, the libraries are only used if openssl is built statically. Otherwise, phar directly calls openssl_verify or openssl_sign. >> > > By the way, any reason why phar is built statically by default? Hi, phar is enabled by default in order to fully test it prior to the first RC. I proposed[1] that a final vote be undertaken just prior to the 5.3RC1 release on phar's ultimate fate. Greg [1] http://www.mail-archive.com/internals@lists.php.net/msg35938.html