Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74411
Return-Path: <ingwie2000@googlemail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 90779 invoked from network); 21 May 2014 13:47:12 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 21 May 2014 13:47:12 -0000
Authentication-Results: pb1.pair.com smtp.mail=ingwie2000@googlemail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=ingwie2000@googlemail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 74.125.83.44 as permitted sender)
X-PHP-List-Original-Sender: ingwie2000@googlemail.com
X-Host-Fingerprint: 74.125.83.44 mail-ee0-f44.google.com  
Received: from [74.125.83.44] ([74.125.83.44:48768] helo=mail-ee0-f44.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 78/29-24198-F5EAC735 for <internals@lists.php.net>; Wed, 21 May 2014 09:47:12 -0400
Received: by mail-ee0-f44.google.com with SMTP id c41so1616492eek.31
        for <internals@lists.php.net>; Wed, 21 May 2014 06:47:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlemail.com; s=20120113;
        h=content-type:mime-version:subject:from:in-reply-to:date:cc
         :content-transfer-encoding:message-id:references:to;
        bh=goHBAo4457MUHfkYF6LsGAT2YqVx63f/BYmsSQkGfkg=;
        b=g4282RGkLGqjcZxJEGujvHbZZ3yth40rsmHaGq+PXim4JpmOUBY5rcx8RqnQIL6G4M
         CWY4aj1LIs/JM7syw/126+dGKqOeAliXThzZSYIsxDbtXlTZ7IShU+kSlOL0q7KtKTml
         SfM3KZyqB8Jmjzly6Herm4pPREG7aWJSbV6gEPiROPt4SDCq9FvGiWwbo688oe4raCkU
         BFkwfoNJ4SPlsfe+x1qj6LjhXk68c5ISXSLeP/TmaWWnF7Abb3wJZmffcSZEisrnH6eS
         U3Cq1CGof9Hi3Sr2XVoQQ2SrzDGnI1CnPyzGHPDQXxxSV5RReZxzulbMGvw85J1jat63
         HeLA==
X-Received: by 10.14.224.72 with SMTP id w48mr4333028eep.63.1400680028442;
        Wed, 21 May 2014 06:47:08 -0700 (PDT)
Received: from [192.168.200.241] (dslb-088-068-163-150.pools.arcor-ip.net. [88.68.163.150])
        by mx.google.com with ESMTPSA id x45sm12052368eee.37.2014.05.21.06.47.07
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Wed, 21 May 2014 06:47:07 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
In-Reply-To: <6048BA05-CC13-46DD-8439-9CB4EE29078B@ajf.me>
Date: Wed, 21 May 2014 15:47:05 +0200
Cc: Nicolai Scheer <nicolai.scheer@gmail.com>,
 PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <9EBA95A7-B9F7-41F0-AE2B-283260753E5A@googlemail.com>
References: <CAOg_pRQxKsJPgFaZ6_y7Rf1i4Bfkbx+FhCxuBtE9PWu58uOfOQ@mail.gmail.com> <6048BA05-CC13-46DD-8439-9CB4EE29078B@ajf.me>
To: Andrea Faulds <ajf@ajf.me>
X-Mailer: Apple Mail (2.1874)
Subject: Re: [PHP-DEV] encode php scripts with opcache compatibility
From: ingwie2000@googlemail.com (Kevin Ingwersen)


Am 21.05.2014 um 15:28 schrieb Andrea Faulds <ajf@ajf.me>:

>=20
> On 21 May 2014, at 11:20, Nicolai Scheer <nicolai.scheer@gmail.com> =
wrote:
>=20
>> I'm currently facing the situation, that I need to protect my php =
sources
>> and retain opcache compatibility.
>=20
> =93Protect=94? Why? Are you trying to ship a product to customers =
which will be run by them, and not have them view the source?
>=20
> In which case, what=92s wrong with obfuscation?
There are decent obfuscators? =85 have not seen any.
And then, obfuscated code can be reversed still, whilst =84sort of=93 =
compiled code is far harder to reverse engeneer.