Re: Code Security
| From: | Ethan Rosenberg | Date: | Fri, 06 Feb 2015 04:24:06 +0000 |
| Subject: | Re: Code Security | ||
| References: | 1 2 3 4 | Groups: | php.db |
| Request: | Send a blank email to php-db+get-48948@lists.php.net to get a copy of this message | ||
On 02/05/2015 11:04 AM, Bastien Koert wrote:
I'm with the two Richard's on this, those users shouldn't have telnet access to the host server at all. Users should be using the browser to access your site. Other than that, the most important thing you can do is to regularly back up your code and database to another location so that if something happens to the working box (and likely all tech products, its not IF its WHEN) you can restore the code and database with minimal data loss Bastien On Thu Feb 05 2015 at 9:39:43 AM Omar Muhsin <mrfroasty@gmail.com> wrote:---- Thanks to all. I apologize, but I did not properly define the problem I am addressing. I have written code for a POS [Point Of Sale] system to be used in a store. I don't expect the store owner to play with the code. His friends [or enemies] might try. There are two logins to the computer, ethan [me] and worker. Worker has to be able to access the code to use it. He has to be blocked from reading, writing or copying the code. How?? TIA EthanYou forgot this one "keep the box OFFLINE ... best security" :-D On 05-02-15 14:10, Richard Quadling wrote:1 - Don't allow terminal access to your box. 2 - Use a PHP byte code encoder (IonCube, Zend Guard) - not perfect astheycan be reversed to access the code in a form. 3 - Don't use PHP.