From owner-freebsd-ports@FreeBSD.ORG Sun May 9 16:38:42 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3CD116A4CE for ; Sun, 9 May 2004 16:38:42 -0700 (PDT) Received: from straycat.dhs.org (h0050da134090.ne.client2.attbi.com [24.91.148.154]) by mx1.FreeBSD.org (Postfix) with SMTP id D095B43D41 for ; Sun, 9 May 2004 16:38:41 -0700 (PDT) (envelope-from tmclaugh@sdf.lonestar.org) Received: (qmail 9099 invoked from network); 9 May 2004 23:40:42 -0000 Received: from unknown (HELO ?192.168.1.100?) (192.168.1.100) by 192.168.1.102 with SMTP; 9 May 2004 23:40:42 -0000 From: Tom McLaughlin To: Thomas-Martin Seck In-Reply-To: <20040509222657.1008.qmail@laurel.tmseck.homedns.org> References: <20040509222657.1008.qmail@laurel.tmseck.homedns.org> Content-Type: text/plain Message-Id: <1084145968.57587.63.camel@compass> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 09 May 2004 19:39:29 -0400 Content-Transfer-Encoding: 7bit cc: freebsd-ports@freebsd.org Subject: Re: current qmail-scanner port with clamav and f-prot fails on 4testvirus.org messages X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 May 2004 23:38:43 -0000 On Sun, 2004-05-09 at 18:26, Thomas-Martin Seck wrote: > * Tim Bishop [gmane.os.freebsd.devel.ports]: > > > 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. > > How about adding an example script to the port that fetches the updated > signatures and that can be customized and cron(8)'ed by the administrator > as desired? (Since I do not use these ports I do not know whether such a > script is already supplied either by the port or by the vendor.) I'm joining this thread late too... There already is a script called check-updates.pl included with the f-prot port. It's in ${PREFIX}/f-prot/tools/check-updates.pl. It's mentioned in the f-prot-sig pkg-message so people can update their sigs as often as they need to without waiting for an update in the ports tree. The vscan/uvscan-dat ports are the same way and include their own script to do the same. For f-prot and vscan a user has the option of either maintaining their sigs via the ports tree, which is what I do since I really only need an update during major breakouts and Tim handles that fine, or using the update utilities provided with each virus scanning package if they need regularly updated sigs. Tom