On Fri, Oct 2, 2020 at 10:08 AM David Rodrigues wrote:
>
> Hello folks,
>
> Instead of an opcode without a php source file, that I imagine is to
> protect the code itself, why not a method to encrypt phar files (not like a
> password). I do not know if exists a secure method to decrypt to execute
Hello folks,
Instead of an opcode without a php source file, that I imagine is to
protect the code itself, why not a method to encrypt phar files (not like a
password). I do not know if exists a secure method to decrypt to execute
only, without reveals the original source code, but maybe it could
On Thu, 1 Oct 2020 at 16:13, Dik Takken wrote:
> The only use case I see is to package commercial closed source
> applications as Docker containers. That allows the packager to ship the
> compiled code along with the exact PHP version and configuration that
> can run it reliably.
>
Could this n
On Fri, 2 Oct 2020 at 10:43, €– ”k”k wrote:
> For example, Java,.NET, etc., I mean that opcode compiled files can be
> bound to fixed versions without considering the compatibility of different
> versions.
>
As I said already, this comparison is simply incorrect: both .net and Java
have been ca
Le 01/10/2020 à 18:32, Levi Morrison via internals a écrit :
> Note that for PHP 8.0 we made the system ID change even more than it
> used to because doing so fixes sigsegvs when switching what extensions
> are loaded (common when trialing an APM product, or loading and
> unloading xdebug) when fil
skip the compilation of Opcache, so it also
supports packaging opcode files into the Phar file
发件人: Nikita Popov
发送时间: 2020年10月1日 20:30
收件人: Rowan Tommins
抄送: PHP internals
主题: Re: [PHP-DEV] RFC: execution opcode file without php source code file
On Thu,
On Thu, Oct 1, 2020 at 9:14 AM Dik Takken wrote:
>
> On 01-10-2020 14:30, Nikita Popov wrote:
> > It would be good to know what the actual use-case for this is. If the goal
> > here is to distribute pre-compiled PHP code without the source code, then
> > this is not going to work without making th
On 01-10-2020 14:30, Nikita Popov wrote:
> It would be good to know what the actual use-case for this is. If the goal
> here is to distribute pre-compiled PHP code without the source code, then
> this is not going to work without making the opcode format stable (which, I
> think, is pretty unlikely
On Thu, Oct 1, 2020 at 1:44 PM Rowan Tommins
wrote:
> Hi,
>
> On 1 October 2020 10:36:20 BST, "肖 鑫鑫" wrote:
> >I commit a new request path, the request is about execution opcode file
> >without php source code file
> >this RFC provides similar to class file of java and pyo file of python.
> >pat
Hi,
On 1 October 2020 10:36:20 BST, "肖 鑫鑫" wrote:
>I commit a new request path, the request is about execution opcode file
>without php source code file
>this RFC provides similar to class file of java and pyo file of python.
>patch is: https://github.com/php/php-src/pull/6146
I'm sure someone w
Hi list !
I would support such a feature as well.
I am working on an implementation that would integrate PHAR support and
opcode cache binary files
(so that you could make a PHAR file that contains binary (opcode cache)
files)
I am voicing my opinion here because the current PHAR implementat
Hi,
czw., 1 paź 2020 o 11:36 肖 鑫鑫 napisał(a):
> I commit a new request path, the request is about execution opcode file
> without php source code file
> this RFC provides similar to class file of java and pyo file of python.
> patch is: https://github.com/php/php-src/pull/6146
I had exact the
12 matches
Mail list logo
