> Thanks for the reply. I am trying to implement PHP in a very secure > environment. My security department wants our developers to only be able to > use functions from an approved list. My plan was to scan any PHP files when > they get saved, get a list of the functions used and compare those to the > "approved" list. The problem is that many of the functions that would not be > available for general use need to be used by some "master scripts" in the > same directory, so I can't use disable_function...
But you can disable_functions with a granularity right down to the file level using the standard httpd.conf semantics. -Rasmus -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
