Re: perl configuration problem

2004-06-22 Thread William McKee
Hi Kemin, I do not think that your taint problems are related to setgid. My experience with taint has taught me not to trust the error output. In this case, you are using ModPerl::Registry which means that your script could be the one which is supplying tainted data. Are you sure that you are unta

perl configuration problem

2004-06-22 Thread Kemin Zhou
First thank a lot for Geoffrey's reply to my previous question. Here I have a very complicated problem that I want to share with you and seeking some opinion. I am using RedHat 9.0. Somehow, some of my perl packages could not be made (the routine perl Makefile.PL generates garbage owing to the ch

RE: IO::File problem on Mod_perl

2004-06-22 Thread Huilli Liu
Thanks Tom. It works now. I forgot "/" between r->document_root() and "templates/quickquote.templ". Great help! Willy -Original Message- From: Huilli Liu [mailto:[EMAIL PROTECTED] Sent: Thursday, June 17, 2004 10:40 AM To: Tom Schindl Cc: [EMAIL PROTECTED] Subject: RE: IO::File probl

reading from STDIN in startup.pl

2004-06-22 Thread Chris Ochs
In startup.pl I read a passphrase from STDIN into a global variable, but the global is undef outside of startup.pl. If I set the global with just a simple assignment ($global::pass = 'pass') it works fine and is visible in my handlers. Is there some sort of tainting or something going on when re

OT: mod_perl mail caught in spamtrap

2004-06-22 Thread Frank Maas
Just so you know... mail.apache.org (aka hermes.apache.org with IP 209.237.227.199) is listed in a SPEWS list (Level 1 to be exact, see http://www.spews.org/ask.cgi?x=209.237.227.199). Unfortunately this means that mail from the mod_perl list, that is sent through this server, can be marked SPAM

Re: Possible Bug: mod_perl version 1 conflict with IBM Websphere Apache plugin

2004-06-22 Thread Geoffrey Young
[EMAIL PROTECTED] wrote: > I have been investigating this problem further. > > The problem appears to be if any module tries to set an environment > variable during the first init run then it will get wiped out by the > shutdown of perl. This then means that the during the second init run > the

Possible Bug: mod_perl version 1 conflict with IBM Websphere Apache plugin

2004-06-22 Thread darren.heather
I have been investigating this problem further. The problem appears to be if any module tries to set an environment variable during the first init run then it will get wiped out by the shutdown of perl. This then means that the during the second init run the environment variable will not exist