Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:38518 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 8350 invoked from network); 22 Jun 2008 20:35:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Jun 2008 20:35:23 -0000 Authentication-Results: pb1.pair.com smtp.mail=martin.jansen@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=martin.jansen@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.234 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: martin.jansen@gmail.com X-Host-Fingerprint: 209.85.198.234 rv-out-0506.google.com Received: from [209.85.198.234] ([209.85.198.234:13934] helo=rv-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 15/33-23032-A87BE584 for ; Sun, 22 Jun 2008 16:35:23 -0400 Received: by rv-out-0506.google.com with SMTP id g37so7592141rvb.23 for ; Sun, 22 Jun 2008 13:35:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=pTNCnoh3i+R7kcocpg43qMXDqhTbMoyxO5Dc/jdYEVs=; b=amxCUtMmLSeGp6dxv7Jn8Wo5NOIoDCDXZGBBUeUBeoHDilSVSd9W85yXpFmqjJdA9Z oYyRp39TB9gKzzyiyOP9rxmlPlbw5di01WZBM7TI1kwnYpMlS/FunmXnsDKkrvrQGiOQ KgVT8I3b0qsH6eoyEu4EsYC8fZu/+Fe0UlU0M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=h8D1cRM++x2w7KM8biRhqGxAUGDsZVHoFnC+Xs7yBkKQAemASQhHLmQH+z0bCBVczr NpppptAaRz78EDp0Q2cuQhbBKJz7Hn85uHEQG84blFqjESpwbAzLYUfWCyIc06bRU0TL yseeO6VjqscXijKzdWtkcqg8bE8TKVXGBAzqg= Received: by 10.141.89.13 with SMTP id r13mr11487352rvl.88.1214166919844; Sun, 22 Jun 2008 13:35:19 -0700 (PDT) Received: by 10.150.96.1 with HTTP; Sun, 22 Jun 2008 13:35:19 -0700 (PDT) Message-ID: Date: Sun, 22 Jun 2008 22:35:19 +0200 Sender: martin.jansen@gmail.com To: "Steph Fox" Cc: "Greg Beaver" , "Marcus Boerger" , internals In-Reply-To: <028a01c8d4a7$18dd4380$4401a8c0@foxbox> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <028a01c8d4a7$18dd4380$4401a8c0@foxbox> X-Google-Sender-Auth: 466d53132b95ae95 Subject: Re: [PHP-DEV] OpenSSL and Phar From: martin@divbyzero.net ("Martin Jansen") On Sun, Jun 22, 2008 at 10:32 PM, Steph Fox wrote: > 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. Would --with-openssl imply --enable-phar-ssl then? Sounds like a good idea to me. Martin