Taint mode is like insurance. You may never need it, but it costs so little to keep it in, even after you believe you've tested all the possible input paths. Not only that, but future versions of Perl may decide that new things are leaks, and so your program will (rightfully!) bomb when Perl is upgraded. This has happened already, when all globbing in 5.004 was made "taint-unsafe" because
it was discovered that it had always been unsafe to glob because of some
bugs in the c-shell.
-- Randal L. Schwartz, Perl hacker | [reply] |
What's also likely to occur is that someone may be working
on your script after you (e.g. adding functionality) and has to
remember to turn on the -T switch again, which (s)he may not
always remember to do, Thus rendering your "insurance"
null & void :)
-- ar0n || Just Another Perl Joe
| [reply] |
While this may be true in most enviornments, your response
has pricked the nagging sys admin in me to say, "NO production
script should EVER be modified. Maintianing the
development->(Readiness if you can afford it)->Production cycle
is key to stable rapid deployment."
coreolyn Duct tape devotee.
| [reply] |