Tracking down taint problems in mod

BMaximus has asked for the wisdom of the Perl Monks concerning the following question:

This is for someone who has a lot of experience with mod_perl. Up until I recompiled mod_perl today, everything I programmed was fine with the taint check on. Now mod_perl sees it fit to complain that something fails the taint check and I can't seem to track down where the problem is and the error it gives me doesn't help either. Its there a way to make perl or mod_perl fess up as to where the problem lies? I'm pretty much dead in the water until I find and eradicate this problem.

My utmost and gracious thanks for your answer,
BMaximus

Comment on Tracking down taint problems in mod_perl

Replies are listed 'Best First'.
(tye)Re: Tracking down taint problems in mod_perl by tye (Sage) on Apr 25, 2001 at 08:56 UTC
Check the Changes* files for the Perl distribution that you just built into mod_perl. There was at least one thing that was being overlooked by taint checks that is being caught in the latest versions of Perl. The details of this change may be a big clue what to look for. I somehow think it will be hard to get assistance from mod_perl on nailing this down. So I'd run the script using "regular" Perl of the same version that you just built into mod_perl and see if the same problem appears. If so, I'd use the perl debugger to get more details. - tye (but my friends call me "Tye")	[reply]
Re: (tye)Re: Tracking down taint problems in mod_perl by BMaximus (Chaplain) on Apr 25, 2001 at 10:22 UTC
Ok! This is realy weird and its freakin me out! I haven't done a thing to my code and all I did was stop the server for an hour and then started it again. Guess what. No complaints from taint. Is perl like this usualy? Damn thing was fickle on me today. BMaximus	[reply]