On 06/28, Yves Goergen wrote:
> for 3 days now, the daily sa-update job fails with the following message
> through Anacron:
That's about how long sa-updates have been working. It's quite possible
you broke something while sa-updates weren't happening, and are just now
seeing it because they're being published again.
> > /etc/cron.daily/spamassassin:
> > Insecure $ENV{TERM} while running with -T switch at /usr/bin/sa-update line
> > 710.
> > sa-update failed for unknown reasons
>
> What does that mean? In that file and line, it's trying to execute GPG,
The -T is referring to perl's taint mode.
'If you try to do something insecure, you will get a fatal error saying
something like "Insecure dependency" or "Insecure $ENV{PATH}".'
- http://search.cpan.org/~jesse/perl-5.14.1/pod/perlsec.pod
"You can’t use system(), exec(), or a piped open in a setuid
or setgid script if any of $ENV{PATH}, $ENV{IFS}, $ENV{CDPATH},
$ENV{ENV}, $ENV{BASH_ENV} or $ENV{TERM} are derived from data supplied
(or potentially supplied) by the user. The script must set the path to
a known value, using trustworthy data."
- http://iderror.com/errors/perl/insecure-envs-while-running-s/
Not sure exactly why you're getting that error.
--
"Forget not that the earth delights to feel your bare feet and the winds
long to play with your hair." - Kahlil Gibran
http://www.ChaosReigns.com
