Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121025
MIME-Version: 1.0
References: <CAEwRQKassuxwi6yRT+s8fenG5vdJhxomRNBvBV0Z-51H_mJ_dA@mail.gmail.com>
 <CAEYWF=4=TciGS3TLh43gt6_GFA_wHmtZBfzHfX_bLxFXytD=dQ@mail.gmail.com>
In-Reply-To: <CAEYWF=4=TciGS3TLh43gt6_GFA_wHmtZBfzHfX_bLxFXytD=dQ@mail.gmail.com>
Date: Sat, 9 Sep 2023 01:18:12 -0300
Message-ID: <CAEwRQKarPaQGviuGDGMZNdDGmivF7RkcaD4vWcdESpUEOGPDTw@mail.gmail.com>
To: bishop@php.net
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] FFI in PHAR files
From: carlosv775@gmail.com (Vinicius Dias)

Ah, that makes total sense. I was worried I was doing something very wrong.=
 haha

Thank you very much for the detailed clarification.

This doesn't seem to be a "critical" feature, but I wonder if the
documentation shouldn't mention something about only "regular files"
being supported.

Vinicius Dias,
Zend Certified Engineer,
iMasters PHP Certified Professional



Vinicius Dias,
Zend Certified Engineer,
iMasters PHP Certified Professional




Em sex., 8 de set. de 2023 =C3=A0s 16:55, Bishop Bettini <bishop@php.net> e=
screveu:
>
> On Fri, Sep 8, 2023 at 2:33=E2=80=AFPM Vinicius Dias <carlosv775@gmail.co=
m> wrote:
>>
>> I was playing around with some libraries using FFI and I wanted to
>> share a .phar with the result, but to my surprise, it didn't work.
>>
>> Apparently we are not able to load shared libraries using FFI from
>> within .phar files.
>> Is that the expected behavior or is it a bug in the FFI extension?
>>
>> I have setup a dummy repo so the error could be easily reproduced:
>> https://github.com/CViniciusSDias/ffi-phar-problem
>>
>> I am sorry if this is not the list to send this type of problem. I
>> will gladly move the thread to the right one if someone points it out.
>>  https://www.php.net/unsub.php
>
>
> Erstwhile PHAR extension maintainer here. What an interesting question! T=
he short answer is no, FFI does not support loading dynamic libraries conta=
ined within a PHAR archive.
>
> The longer answer is that FFI was not written to be able to support VFS l=
ocations, including the phar:// scheme. In this case, PHP starts and invoke=
s the code. The code invokes FFI[1] with a phar:// path, which then tries t=
o perform a dlopen()[2], which fails because dlopen has no idea how to reso=
lve PHAR paths: dlopen() expects a path that the OS can resolve[3].
>
> I suppose it'd be possible to improve FFI to call the PHP VFS layer to re=
solve a path, which would handle the phar:// scheme and other schemes. But,=
 I would be worried about potential other downstream impacts - esp. securit=
y implications - as this is a novel (to me at least) scenario.
>
> bishop
>
> [1]:https://github.com/php/php-src/blob/50ca24251d97dbf78b0c1165dac7c1a19=
ff1c87a/ext/ffi/ffi.c#L2968C3-L2968C3
> [2]:https://github.com/php/php-src/blob/50ca24251d97dbf78b0c1165dac7c1a19=
ff1c87a/Zend/zend_portability.h#L156
> [3]:https://man7.org/linux/man-pages/man3/dlopen.3.html
>