<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Thu, 23 May 2013 04:40:03 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Sjon.Blog:  Protecting your property (PHP Encryption)]]></title>
      <guid>http://www.phpdeveloper.org/news/4584</guid>
      <link>http://www.phpdeveloper.org/news/4584</link>
      <description><![CDATA[There's always been several PHP developers out there looking to protect the source that they so lovingly crafted. They look for alternatives to keeping it safe, but sometimes it's just not enough. In <a href="http://sjon.hortensius.net/blog/2005/12/protecting-your-property">this new post</a> on the Sjon.Blog today, he mentions some of the frustrations he's had already with exectly this.
<p>
<quote>
<i>
Zend almost convinced me that their <a href="http://www.zend.com/store/products/zend-safeguard-suite.php">Safeguard Suite</a> really secured your PHP scripts. Ofcourse I know that scripts need to be interpreted and executed and are therefore never 100% safe; but I expected some form of obfuscation and rewriting to prevent this. This <a href="http://www.phpdecode.com/">doesn't seem</a> to be the case though. I have had a look at <a href="http://pobs.mywalhalla.net/">PHP Obfuscator/Obscurer</a>, but a good illustration of the quality of that script can be illustrated with a simple, readable example.
<p>
Also, obfuscating <a href="http://www.react.nl/">React</a> took me almost an hour; which isn't that strange when you have had a look at the sourcecode. 
</i>
</quote>
<p>
As far as I've heard/seen so far, there's not really a good solution to <a href="http://sjon.hortensius.net/blog/2005/12/protecting-your-property">this dilema</a>. Sure, some are better than others, but there's still a hole there that is just waiting to be filled with an application anyone can use...]]></description>
      <pubDate>Fri, 30 Dec 2005 07:15:19 -0600</pubDate>
    </item>
  </channel>
</rss>
