Update suddenly fails "for unknown reasons"

[Yves Goergen <no...@unclassified.de>]

Hi,

for 3 days now, the daily sa-update job fails with the following message
through Anacron:

> /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,
which should be totally unrelated. I haven't touched the SA
configuration for the last 6 days and then I just added one more
blacklist_from rule. These were almost the last commands in the server's
terminal window.

SpamAssassin itself still works normally.

Running Ubuntu 10.4 Server x64 with SpamAssassin 3.3.1-1.

-- 
Yves Goergen "LonelyPixel" <no...@unclassified.de>
Visit my web laboratory at http://beta.unclassified.de

Re: Update suddenly fails "for unknown reasons"

[da...@chaosreigns.com]

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

Re: Update suddenly fails "for unknown reasons"

[Michael Scheidell <mi...@secnap.com>]

On 6/28/11 4:17 PM, Yves Goergen wrote:
> Insecure $ENV{TERM} while running with -T switch at /usr/bin/sa-update line 710.
did you possibly restart cronjob from cli? and it sucked in the ${TERM} 
env variable from your console?


-- 
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
 >*| *SECNAP Network Security Corporation

    * Best Mobile Solutions Product of 2011
    * Best Intrusion Prevention Product
    * Hot Company Finalist 2011
    * Best Email Security Product
    * Certified SNORT Integrator

______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r). 
For Information please see http://www.secnap.com/products/spammertrap/
______________________________________________________________________