Re: Securing PHP code..

> > If you mean to protect your source from your users, that is the case > already. Unless someone can compromise your server, they never get access > to the source, only its output. > True! But what for the network technicians, system administrators and web developers (to be very paranoid) that access the servers. Having a background as a system admin and network techie, I know too well of the too-often slack control of those accessing servers. Hacking has become so much more of a pain with PHP and all the possibilities it suggests (for those creating server extensions). > This is far different from standard client-side applications, where the > user has a compiled version of the source. With server-side applications, > there is nothing for them to reverse engineer. Yes, of course.. but with compiled software (built using asm, C/C++, VBA or what have you), it doesn't matter where the software is - on the user's computer or the server. All the same, it's compiled and a tough business to reverse engineer and make sense of. > Hope that helps. > > Chris It does! Seeing that you have the additional title "hacker" at your site I'm sure you know of my despair when it comes to internal hacking. ;-) All the best, VPeO