autoupdate confusion?

[Kevin Spicer]

On Sat, 2003-11-01 at 16:38, Jim Flowers wrote:

>I studied update_virus_scanners as a possible undocumented? solution
>but it
>has a number of problems:

Its actually the default and offically 'correct' way of doing it for
MailScanner (but the install docs on the site do seem to be out of date
in this respect).  Its used automatically on rpm installs.

>1. It expects virus_scanners.conf to have three fields; the one in my
>distribution has only two.  Without the PACKAGEDIR field, it will do
>nothing as written.

Then you have a version mismatch between upgrade_virus_scanners and
virus_scanners.conf.  For the current version of MailScanner the
PACKAGEDIR field should be present in virus_scanners.conf.

>2. If the PACKAGEDIR field is present, the x$1 test in the
>clamav-wrapper
>program will fail as $1 is passed as PACKAGEDIR, not -IsItInstalled.

Not if you have the same version of that script I have.  Its called
as...
clamav-wrapper $PACKAGEDIR -IsItInstalled

The PACKAGEDIR is extracted from $1 then the arguments are shifted to
make %1 = "-IsItInstalled"

Maybe your version of update_virus_scanners is more recent than your
version of MailScanner?  The addition of PACKAGEDIR is a recent one and
there were changes to MailScanner, the wrapper and autoupdate scripts
and update_virus_scanners to support it.

>These are easy enough to fix for a shell hacker and even easier to just
>run
>the freshclam wrapper directly,

You definitely should use update_virus_scanners if possible to ensure
that mail isn't scanned during the update process.






BMRB International
http://www.bmrb.co.uk
+44 (0)20 8566 5000
_________________________________________________________________
This message (and any attachment) is intended only for the
recipient and may contain confidential and/or privileged
material.  If you have received this in error, please contact the
sender and delete this message immediately.  Disclosure, copying
or other action taken in respect of this email or in
reliance on it is prohibited.  BMRB International Limited
accepts no liability in relation to any personal emails, or
content of any email which does not directly relate to our
business.