Commit graph

9 commits

Author SHA1 Message Date
Alexander Leidinger
4171a9b485 Use the @FreeBSD.org address of the maintainer.
Approved by:	marius
2004-04-20 13:49:29 +00:00
Alexander Leidinger
d8678b1f94 - H+BEDV GmbH released a new tarball of the beta version shipping an updated
anti-virus engine (6.23.0.3 -> 6.25.0.2), current virus definition file
  (6.23.0.49 -> 6.25.0.1) and an updated antivir.conf.
  If you are using the auto-update facility you should already have the
  updated AV engine binary and VDF.
- Look for the libmilter of the Sendmail port and the GnuPG binary in
  LOCALBASE instead of PREFIX.

Submitted by:	Marius Strobl <marius@alchemy.franken.de>
2004-04-12 12:53:50 +00:00
Alexander Leidinger
078dd2cc19 - Use daemon(8) for launching avmilter in order to detach it from the
controlling terminal. [1]
- Make the avq script check if it's ran by the avmilter user in addition
  to uid == 0. This enables `avq --remove` to be run via a script and the
  ExternalProgram option in order to automatically delete the rejected
  messages. [2]
- Install a script avqrm which serves this purpose, i.e. executes
  `avq --remove` and can be run via ExternalProgram.
- Make the avq script not print the contents of the queue when option
  '--remove' is given, this greatly improves speed and otherwise it's not
  really suitable to be called on every rejected message. Fix some typos.
- Fix pkg-plist by adding antivirupdater.

Requested by:	ache [1], [2]
Submitted by:	maintainer
2004-03-08 08:03:50 +00:00
Alexander Leidinger
499270998d HEADS-UP: When updating from a previous version you have to do the following
after deinstalling the old port:
	  # rm PREFIX/AntiVir/antivir
	  # rm PREFIX/AntiVir/antivir.vdf
	  # chown root:wheel PREFIX/AntiVir
	  # chown root:smmsp PREFIX/AntiVir/hbedv.key
	  In your SENDMAIL_MC change
	    `S=unix:PREFIX/AntiVir/avmilter.sock, F=T, T=S:10m;R:10m;E:5m'
	  to:
	    `S=unix:/var/spool/avmilter/avmilter.sock, F=T, T=S:10m;R:10m;E:10m'
	  and rebuild sendmail.cf.
	  If /var/spool/avmilter exist you have to:
	  # chown -R smmsp:smmsp /var/spool/avmilter
	  If you are using a customized PREFIX/etc/avmilter.conf the port
	  won't remove it on deinstall and you have to manually change User
	  and Group to smmsp there.
	  Afterwards you can install the new version of this port. You then
	  should run antivirupdater to get a current VDF.

- Change ownership of the socket to user and group smmsp as expected by
  sendmail. This involves running the milter as smmsp:smmsp, changing the
  ownership of rest of the files and moving the socket to /var/spool/avmilter
  but fixes the "local socket unsafe" problem. [1]
- Move the milter into the background when launching, this solves the problem
  with disappearing socket on boot. [2]
- Update to 1.1-beta which fixes the "Bad file descriptor" problem. For
  a full list of chances see ChangeLog in the DOCSDIR. [3]

Suggested by:	ache@ [1], [3]
Suggested by:	Martin P. Hellwig <mhellwig@xs4all.nl> [2]
Submitted by:	maintainer
2004-03-05 15:08:29 +00:00
Alexander Leidinger
ec2b2cf02e - H+BEDV GmbH released a new tarball shipping an updated anti-virus engine
(6.23.0.1 -> 6.24.0.2), current virus definition file (6.23.0.1 -> 6.24.0.6)
  and an updated antivir.conf adding the new option "UpdaterKeepsBackups" for
  for the current AV engine.
  If you are using the auto-update facility you should already have the
  updated AV engine binary and VDF.
- Install the original AV engine binary and the VDF from the tarball with
  suffix "-dist_avfbmlt" instead of "-dist" so ${PREFIX}/AntiVir/antivir
  can be shared between different H+BEDV AntiVir products without conflicts.
- Add another instance to MASTER_SITES.

Submitted by:	marius
2004-02-20 16:48:54 +00:00
Alexander Leidinger
16eda7f1f8 - H+BEDV GmbH released a new tarball shipping an updated anti-virus engine
(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>
2003-12-10 17:57:57 +00:00
Alexander Leidinger
d4a3fdc5e9 - Install the virus definition file and the actual virus scanner with the
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.
2003-11-17 10:15:43 +00:00
Alexander Leidinger
0a0d69f8c1 - H+BEDV GmbH released a new tarball shipping an updated anti-virus engine
(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
2003-10-14 16:04:48 +00:00
Alexander Leidinger
625b606c95 Add AntiVir Milter, a mail virusscanner using the Sendmail Mail Filter API.
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>
2003-09-24 13:47:38 +00:00