in reply to Re^2: Runtime Taint Enable
in thread Runtime Taint Enable
I agree. It's useful to provide configuration information through the environment, and there's no danger (as long as you don't use environment variables that are set automatically based on the Web request).
I often simply blindly untaint data from environment variables I know are safe, and convert PERL5LIB into a series of use lib commands. That's the technique I would recommend.
It would be useful if Perl's mechanism for handling tainted data was more flexible, to better handle these situations.
|
|---|