(6.22.0.1 -> 6.23.0.1), a current virus definition file (6.23.0.1) and
and updated antivir.conf adding new options for the new features in the
current AV engine.
If you are using the auto-update facility you should already have the
updated AV engine and VDF. The new options available in antivir.conf are
only relevant if you are using the update daemon mechanism (i.e. you are
using `antivir --update-daemon` instead of running antivirupdater via
cron(8)) or you own a true commercial license (i.e. no private license)
and want to catch "unwanted files" e.g. dialers in addition to worms and
viruses.
- Be consistent in how PREFIX gets inserted in the avq script compared to
the other patched files. The old way previously saved a patch which is
no longer true. No change in the installed script.
Submitted by: Marius Strobl <marius@alchemy.franken.de>
write bit turned on as both get updated when using the automated updates
facility. The auto-update mechanism doesn't seem to have a problem if
the write bit is disabled but it's not quite correct.
- Mention in pkg-message that that the virus scanner (referenced as
"anti-virus engine" by H+BEDV) also gets updated when using the automated
updates facility.
(6.21.0.1 -> 6.22.0.1) and a current virus definition file (6.22.0.0).
If you are using the auto-update functionality you should already have
these updated versions.
- Mention the AntiVir Bulletin Board (support) in the DESCR.
- Make the antivirupdater script behave like described in the documentation
(pass command line arguments to antivir).
- Make the avq script check for uid == 0, the avmilter spool directory can't
be read without sufficient permissions.
Submitted by: maintainer
This is a commercial stand-alone solution written in C not a PERL script +
myriads of dependencies + some AV...
Licenses for private (individual, non-commercial) use, e.g. for protecting
your family's home network, can be applied for free of charge.
Submitted by: Marius Strobl <marius@alchemy.franken.de>