php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #52819 Compling/Encoding
Submitted: 2010-09-12 01:34 UTC Modified: 2010-09-12 01:46 UTC
From: dmewis at agaresmedia dot com Assigned:
Status: Not a bug Package: *General Issues
PHP Version: Irrelevant OS: Lindux
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: dmewis at agaresmedia dot com
New email:
PHP Version: OS:

 

 [2010-09-12 01:34 UTC] dmewis at agaresmedia dot com
Description:
------------
Huge problem is developing that will affect affordability of software online.  The support staff for phpShield says they can't deploy their compiling/encryption software so that the phpShield loaders can be installed in the user's webspace rather than the root level.  This is a huge problem when we are faced with heavy software theft because we are forced into open source.  Because PHP almost forces people who use it to write in open source, there are not enough quality software out there except those that use ZendGuard, phpShield, or other byte-code encrypter/encoders that forces hosts to install the loaders at the root level. 

It is critical for future of software development that there be a way to install byte code encryption loaders IN THE section between the root level and public_html which I refer to as part of the user webspace.  We should not be forced to pay a grand a year to Zend for their software, nor should we have to battle website hosts who refuse to install loaders on behalf of their customers.  It needs to be made possible that we can finally run byte-code compiled software without a lot of hassle or having to have root level access.  Otherwise, it's difficult to sell software to webmasters using shared accounts.

Now, I would of posted this as a suggestion, but the PHP development team provides no way of contacting them.  Hopefully this gets read by the right person.


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2010-09-12 01:46 UTC] rasmus@php.net
-Status: Open +Status: Bogus
 [2010-09-12 01:46 UTC] rasmus@php.net
Cry me a river.
 [2010-09-12 02:56 UTC] zippy1981 at gmail dot com
First of all, this is not a new problem, so I don't see how it "will affect 
affordability of software online." If you argued "fixing" this long standing 
issue, "will affect software afford ability," that would make some sense.

Secondly, I think what you are saying is you want you customers, who are PHP 
developers to be able install your PHP libraries, as bytecode, on their shared 
hosting servers. However, phpShield cannot be installed unto the shared webhost 
your customer is using.

The problem is even if changes were made to php and phpShield to allow this to 
happen, ISPs would have to configure PHP to enable these features. It seems liek 
it would be easier to find shared hosting that has phpShield installed globally. 
I would suggest contacting phpShield and asking that.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Mon May 06 07:01:32 2024 UTC