Date: Sun, 09 May 2004 22:57:44 +0100 From: Tim Bishop <tim@bishnet.net> To: Rick Updegrove <dislists@updegrove.net> Cc: ports@FreeBSD.ORG Subject: Re: current qmail-scanner port with clamav and f-prot fails on 4testvirus.org messages Message-ID: <409EA958.5030402@bishnet.net> In-Reply-To: <407D4CFE.3060500@updegrove.net> References: <407C61FA.8070701@updegrove.net> <407C9C7A.9070304@mac.com> <407D4CFE.3060500@updegrove.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig54DEAB069F593AD6244BC76C Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Rick Updegrove wrote: > The current qmail-scanner port with clamav and f-prot both scanning for > viruses fails on 4 of the testvirus.org messages. > Lastly, my point is these "ports" are all current according to > "portupgrade -rva" and have current virus definitions yet the > combination allow viruses to get through. This seems somewhat relevant > to FreeBSD ports to me. > > So now that we have cleared up a few things, who wants to discuss a > strategy to maintain an effective FreeBSD virus-scanner port for qmail? Sorry - a late reply to this thread. I maintain the f-prot port, and the definitions for it. I like to think I keep the f-prot up-to-date as best I can (currently it's one minor revision behind, and there's a PR waiting to sort that out). However, the definitions are a harder thing to solve. The f-prot guys update the definitions on an almost daily basis. Should I be updating the port that often? I suspect not. A better strategy would be for users of the port to keep the definitions up-to-date manually. A good middle ground (which I'm trying to do a better job of) is updating the definitions when a "big" virus goes around. I guess I could also try and update them if they haven't been updated in a "while". Any thoughts? Tim. -- Tim Bishop http://www.bishnet.net/tim PGP Key: 0x5AE7D984 --------------enig54DEAB069F593AD6244BC76C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFAnqldfc7WWVrn2YQRAimEAKCNURPRowRiZDP5etzAha6F07e0fgCgjPL5 1O688kdBrCLNrgpLqEFLgxI= =YhZN -----END PGP SIGNATURE----- --------------enig54DEAB069F593AD6244BC76C--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?409EA958.5030402>