Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74422 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 29760 invoked from network); 21 May 2014 22:53:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 May 2014 22:53:15 -0000 Authentication-Results: pb1.pair.com header.from=derick@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=derick@php.net; spf=unknown; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.113.146.227 as permitted sender) X-PHP-List-Original-Sender: derick@php.net X-Host-Fingerprint: 82.113.146.227 xdebug.org Linux 2.6 Received: from [82.113.146.227] ([82.113.146.227:57005] helo=xdebug.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AB/93-00924-95E2D735 for ; Wed, 21 May 2014 18:53:14 -0400 Received: from localhost (localhost [IPv6:::1]) by xdebug.org (Postfix) with ESMTPS id 85CB6DEAF0; Wed, 21 May 2014 23:53:08 +0100 (BST) Date: Wed, 21 May 2014 17:53:04 -0500 (CDT) X-X-Sender: derick@whisky.home.derickrethans.nl To: Nicolai Scheer cc: Rasmus Lerdorf , Andrea Faulds , Kevin Ingwersen , PHP Internals In-Reply-To: Message-ID: References: <6048BA05-CC13-46DD-8439-9CB4EE29078B@ajf.me> <9EBA95A7-B9F7-41F0-AE2B-283260753E5A@googlemail.com> <537CBD67.4000008@lerdorf.com> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] encode php scripts with opcache compatibility From: derick@php.net (Derick Rethans) On Wed, 21 May 2014, Nicolai Scheer wrote: > Do you have an example of a tool that can reverse opcodes to php code? > Maybe I did not search for the right thing, I did not stumble upon any. It exists, there are tools. I might have seen code that does it. > I always thought the opcodes where kind of cryptic, at least a bit... I'm > not longing for "true" protection. It's enough if the scripts can not be > read and modified in an easy way. Yes, that is definitely possible. I actually have a working extension for PHP 5.3 and 5.4 that stores encrypted opcodes. PHP 5.5 not yet implemented. > All I'm asking for is a way do so in way, that scripts are still > cacheable (even if this makes dumping the opcodes easier...). Yes, correct. You can get to the opcodes, it's not difficult, it even works with VLD, that you mention here: > I found Derick's Vulcan Logic Disassembler, I think this can help my > understanding of what opcodes of a script look like. cheers, Derick