On Thu Mar 14 15:16:05 2013, jhiller wrote:
Show quoted text> In taint mode I have to unset $ENV{PATH}, making the module's calls to
> `crontab ...` fail. Taint mode makes it necessary to use the full path, for
> example `/usr/bin/crontab ...`
If you set your $ENV{PATH} to "/usr/bin" (or wherever your crontab binary is), will it pass taint
checks? The "Cleaning Up Your Path" section of `perldoc perlsec` suggests that will work. Let
me know.
Scott