Taint checking at the command line in Win32

I'm not sure this is the right place for a post like this, so please correct me if it isn't (msg me in the CB).
I've seen a lot of people asking the question: "Why do I get the error message 'Too late for -T option' when running a script from the command line on perl for Win32?" I found that if you use -T in the shebang line as well as on the command line, it doesn't give that error. Hope this helps.

Stamp_Guy
Computers aren't intelligent, they just think they are.

Comment on Taint checking at the command line in Win32

Replies are listed 'Best First'.
Re: Taint checking at the command line in Win32 by idnopheq (Chaplain) on May 04, 2001 at 15:10 UTC
Yep ... there are a few ways 'round it. Some are more equal than others ... Modify the file type from Windows/NT Explorer. This will make taint checking permanant, so use this with caution. Go to Tools - Folder Options. Click on the File Types tab, and scroll down until you find PL. Select it and click Edit or Advanced. Select the Open action and click Edit. Add -T after perl.exe but before the "%1". Or, and I like this better, use the runperl.bat or pl2bat.bat, modifying the shebang line after setting the .bat file up to wrap your script. This option makes taint checking specific to the scripts you want, versus the global option above. This method also allows piping, which the .pl file association does not. HTH -- idnopheq Apply yourself to new problems without preparation, develop confidence in your ability to to meet situations as they arrise. ~ Shunryu Suzuki	[reply]
Re: Re: Taint checking at the command line in Win32 by frag (Hermit) on May 04, 2001 at 19:30 UTC
It would really be nice if there was a `use taint;` pragma to deal with this. 15 minutes and one Google search later... Turns out that this has been knocked around on Perl6-language, starting with Re: RFC 288 (v2) First-Class CGI Support. -- Frag.	[reply]