[PHP] Re: Securing PHP code..

2003-11-25 Thread Peter Clarke
Video Populares Et Optimates wrote: Hi! I'm pondering on a problem here. Being a C/C++, Java and Visual Basic developer, the aspect of reverse engineering code from (compiled) programs, hasn't occupied my mind that much. Now, developing PHP scripts on large scale I have started to think

[PHP] Re: Securing PHP code

2003-06-26 Thread SLanger
One more thing, make sure the application is running on its own server meaning don't use a shared hosting enviroment that allows others to gain access to your directories. In this case even placing the file outside of docroot doesnot secure it in anyway since any other user can access it with

[PHP] Re: Securing PHP code

2003-06-26 Thread nad
1) The site will have to take very high traffic and possibly thousands of transactions per hour - Which is the best free db to use (I am guessing MySQL) - Which is the best paid database (Other than MySQL) transactions ??? Go for one which offers commit/rollback ... === 2) I

[PHP] Re: Securing PHP code

2003-06-26 Thread Manuel Lemos
Hello, On 06/26/2003 02:10 AM, Joseph Szobody wrote: A safer architechture would be to use two machines. One to act as the Web server and the other to process transactions. The Web server would take the orders and request the transaction server to process them. The transcation server can only be

Re: [PHP] Re: Securing PHP code

2003-06-26 Thread Mike Morton
Why not just connect the 2 servers together with additional nic cards, then the second is only accessable from the first. On 6/26/03 6:26 PM, Manuel Lemos [EMAIL PROTECTED] wrote: Hello, On 06/26/2003 02:10 AM, Joseph Szobody wrote: A safer architechture would be to use two machines. One to

Re: [PHP] Re: Securing PHP code

2003-06-26 Thread Manuel Lemos
Hello, On 06/26/2003 07:43 PM, Mike Morton wrote: Why not just connect the 2 servers together with additional nic cards, then the second is only accessable from the first. That is the point but if you make the database server accessible from the Web server, anybody that hacks the Web server, can

Re: [PHP] Re: Securing PHP code

2003-06-26 Thread Chris Rehm
Manuel Lemos wrote: That is the point but if you make the database server accessible from the Web server, anybody that hacks the Web server, can hack the information in the database server, making having the two servers pointless. Not necessarily. There are a number of things that one can do to

[PHP] Re: Securing PHP code

2003-06-25 Thread Manuel Lemos
Hello, On 06/26/2003 06:01 AM, Siddharth Hegde wrote: I have tons of other questions going through my mind. I think I should just go and buy a book or something. Any suggestions? I will also be securing the Linux server so any book on this topic also would help (I am sure they are a couple of

[PHP] Re: Securing PHP code

2003-06-25 Thread Joseph Szobody
A safer architechture would be to use two machines. One to act as the Web server and the other to process transactions. The Web server would take the orders and request the transaction server to process them. The transcation server can only be accessed from the Web server. Nobody should