Re: About functions
| From: | Developer | Date: | Tue, 24 Mar 2009 14:33:57 +0000 |
| Subject: | Re: About functions | ||
| References: | 1 2 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-6252@lists.php.net to get a copy of this message | ||
>
> > apc_compile_string(),
>
> There's a feature request for doing something like apc_eval already, I suppose it's
> something that could be added I'm just rightly nervous about eval() in general. Do you have a
> strong use case for this?
>
>
> -shire
Hello,
PHP source is not good for security, and I am thinking about methods to
password difficult (not very difficult) access.
In this way, on memory application compiled (virtual application
directory, all files in memory or 'insecure' files) is not the best
solution, but is better than clear PHP source file.
At this point, some problems:
APC check for existence of file (bad thing for this solution),
apc_compile_string(php_code_string,virtual_filename,
permissions_only_execute) could be a solution. When file is in memory
another program could read file (bad thing).
In this case bad people could see memory (root) but should need some
minutes of work.(not open file with text editor and see the password)
PHP_FUNCTION(apc_bin_dump);
PHP_FUNCTION(apc_bin_load);
PHP_FUNCTION(apc_bin_dumpfile);
PHP_FUNCTION(apc_bin_loadfile);
And this routines are good for performance issues, and 'light-lax'
security (opcode is difficult to read). Opcode never changes do not need
to recompile (on same machine) or check it for change.
All files of application can be loaded in memory with routine.
This is my opinion...
--
--
Publicidad http://www.pas-world.com