ichimunki has asked for the wisdom of the Perl Monks concerning the following question:
I have a script that has -T on the hashbang line. I normally call it using the Unix method ./script.pl (having chmod 7**'ed it). No problem.
The same script generates a taint error at line 1 when executed using "perl script.pl". This stops the program before it gets started. Everything goes back to normal when using "perl -T script.pl" to execute. But this is less than ideal. I don't want everyone who might use the script to have to learn to use the -T switch when executing.
Is there a way to ensure taint checking without having to explicitly explain this to potential users?
The same script generates a taint error at line 1 when executed using "perl script.pl". This stops the program before it gets started. Everything goes back to normal when using "perl -T script.pl" to execute. But this is less than ideal. I don't want everyone who might use the script to have to learn to use the -T switch when executing.
Is there a way to ensure taint checking without having to explicitly explain this to potential users?
|
---|
Replies are listed 'Best First'. | |
---|---|
perl T-shirt and #!/usr/bin/perl -T conflict
by dws (Chancellor) on Jan 25, 2001 at 07:45 UTC | |
by wolfger (Deacon) on Dec 30, 2004 at 20:29 UTC | |
by belg4mit (Prior) on May 22, 2005 at 16:30 UTC | |
Re: perl -T script.pl and #!/usr/bin/perl -T conflict
by rlk (Pilgrim) on Jan 24, 2001 at 23:54 UTC | |
Re: perl -T script.pl and #!/usr/bin/perl -T conflict
by KM (Priest) on Jan 24, 2001 at 23:34 UTC | |
by arturo (Vicar) on Jan 24, 2001 at 23:42 UTC | |
Re: perl -T script.pl and #!/usr/bin/perl -T conflict
by arturo (Vicar) on Jan 24, 2001 at 23:29 UTC | |
Re: perl -T script.pl and #!/usr/bin/perl -T conflict
by japhy (Canon) on Jan 24, 2001 at 23:46 UTC | |
by Kanji (Parson) on Jan 25, 2001 at 07:00 UTC |
Back to
Seekers of Perl Wisdom