Thanks a lot for Stas and Willian comment. Both of you are correct. I figured out my problem:
it came from my program reading a configuration file. When Taint Check (-T in perl or PerlSwitches +T
or TaintCheck On in httpd.conf) is turned on, any file handle is thought to be tainted.
In this case, I knew my script is reading a READ-ONLY configuration file. I used the
IO::Handle::untaint(*MYINPUTFILE) to remove the trouble. Hopfully, this may help the
next person who run into similar situation.
Good.
It looks that you have to be careful when using the taint check.
It would be better to put into the doc somewhere saying if you turn on taint and saw the error message
ModPerl::Registry: Insecure dependency
The go back to your source code and read Perl Security Section of any Perl Book carefully.
We can't possibly document all possible error messages perl may emit. Removing the misleading ModPerl::Registry: prefix is the right solution in this case.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
