Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125289
Precedence: bulk
MIME-Version: 1.0
References: <CAAfnsFUP3OoAYSMe2NCo=SFUNtLQU6DiWddhHaXf5xY09GTr5Q@mail.gmail.com>
 <8664467A-D602-48B6-96CA-D6FAD4488F14@cmpct.info>
In-Reply-To: <8664467A-D602-48B6-96CA-D6FAD4488F14@cmpct.info>
Date: Mon, 26 Aug 2024 21:59:53 +0200
Message-ID: <CAAfnsFVm8NNjoHJog3qch5Lw8On6uRYX7YgMm0N+y6Za5dj1hw@mail.gmail.com>
Subject: Re: [PHP-DEV] Native SSL support in Phar extension
To: Calvin Buckley <calvin@cmpct.info>
Cc: Internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
From: petk@php.net (Peter Kokot)

On Mon, 26 Aug 2024 at 20:05, Calvin Buckley <calvin@cmpct.info> wrote:
> As such, it might be a bit tricky for people on Windows/AIX; the easiest
> solution if PHAR is using the openssl extension's symbols would be to not
> build the openssl extension as shared.

I've just checked Windows build and the PHP downloaded from PHP.net
and it seems to already use the openssl and phar extensions like this.
The ext/openssl is built as shared (the php_openssl.dll) and phar is
built into the php binary (which doesn't matter much here I think).
So I think this means one platform to worry about this issue here less.

About the AIX it's totally possible that this is still an issue. I'll
need to check it out in more detail at some point. If I understand the
issue mentioned in the blog post it is something else - two different
OpenSSL versions being linked. Which is of course bad. And this
removal is moving towards this direction also. OpenSSL being linked
only in ext/openssl. And in PHP different OpenSSL versions linked
could happen in a few other places as well - the curl, ftp and mysqlnd
extensions.

Well, this issue sounds complicated for PHP 8.4, so we can do it in
the next version then.