From owner-cvs-ports@FreeBSD.ORG Tue Aug 17 13:59:06 2004 Return-Path: Delivered-To: cvs-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F3C6C16A4CF; Tue, 17 Aug 2004 13:59:05 +0000 (GMT) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [210.226.20.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50D6E43D45; Tue, 17 Aug 2004 13:59:05 +0000 (GMT) (envelope-from kuriyama@imgsrc.co.jp) Received: from localhost (localhost [127.0.0.1]) by black.imgsrc.co.jp (Postfix) with ESMTP id C968C50BE8; Tue, 17 Aug 2004 22:58:59 +0900 (JST) Received: from black.imgsrc.co.jp (black.imgsrc.co.jp [IPv6:2001:218:422:2::9999]) by black.imgsrc.co.jp (Postfix) with ESMTP id 5550A50BC6; Tue, 17 Aug 2004 22:58:57 +0900 (JST) Date: Tue, 17 Aug 2004 22:58:57 +0900 Message-ID: <7misbhdfxa.wl@black.imgsrc.co.jp> From: Jun Kuriyama To: Oliver Eikemeier In-Reply-To: <730CE1BB-EFA2-11D8-924A-00039312D914@fillmore-labs.com> References: <20040816145901.GB5482@lum.celabo.org> <730CE1BB-EFA2-11D8-924A-00039312D914@fillmore-labs.com> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd 0.1 cc: "Jacques A. Vidrine" cc: cvs-ports@FreeBSD.org cc: cvs-all@FreeBSD.org cc: ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/security/portaudit-db/database portaudit.txt portaudit.xlist portaudit.xml X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Aug 2004 13:59:06 -0000 Hey, can both of you do constructive discussion rather than picking past conflicts? At Mon, 16 Aug 2004 18:36:40 +0200, Oliver Eikemeier wrote: > > What are you trying to accomplish, Oliver? I would really like to know > > because clearly this situation is not good for our community. > > A correctly working port auditing system, where users are timely warned > of possible vulnerabilities in their installed software. While it might > be acceptable when a documentation sometimes leaves out a PORTEPOCH or > has false positives for a couple of days, I consider this highly > problematic for portaudit and try to fix these things ASAP. Both of you are providing good tools for port auditing. Please don't blame someone who did breakage. Let's fix and go ahead. I think you can do emergency fix to security/vuxml/vuln.xml if Jacques cannot reply smoothly. But posting a patch to freebsd-vuxml@ highly desirable. -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project