From owner-freebsd-vuxml@FreeBSD.ORG Tue Aug 17 20:39:17 2004 Return-Path: Delivered-To: freebsd-vuxml@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C21B16A4CE; Tue, 17 Aug 2004 20:39:17 +0000 (GMT) Received: from pittgoth.com (14.zlnp1.xdsl.nauticom.net [209.195.149.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1444843D46; Tue, 17 Aug 2004 20:39:17 +0000 (GMT) (envelope-from trhodes@FreeBSD.org) Received: from localhost (acs-24-154-239-170.zoominternet.net [24.154.239.170]) (authenticated bits=0) by pittgoth.com (8.12.10/8.12.10) with ESMTP id i7HKbh0l076856 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 17 Aug 2004 16:37:44 -0400 (EDT) (envelope-from trhodes@FreeBSD.org) Date: Tue, 17 Aug 2004 16:38:18 -0400 From: Tom Rhodes To: Oliver Eikemeier Message-Id: <20040817163818.1c307c06@localhost> In-Reply-To: <853F2EE0-F086-11D8-A951-00039312D914@fillmore-labs.com> References: <20040817153510.6ccfbd8b@localhost> <853F2EE0-F086-11D8-A951-00039312D914@fillmore-labs.com> X-Mailer: Sylpheed-Claws 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-vuxml@FreeBSD.org cc: "Jacques A. Vidrine" cc: Pete Fritchman Subject: Re: cvs commit: ports/security/portaudit-db/database portaudit.txt portaudit.xlist portaudit.xml X-BeenThere: freebsd-vuxml@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documenting security issues in VuXML List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Aug 2004 20:39:17 -0000 On Tue, 17 Aug 2004 21:49:15 +0200 Oliver Eikemeier wrote: > Tom Rhodes wrote: > > >> Jacques doens't seem to like this: "Aaaaaahh!". I don't really care > >> ident(1) is fine for me, and it seems like this is the only reliable > >> indication. OTOH you'll need a couple of references (file, list of > >> FreeBSD versions). Doable, so when no other ideas pop up we should do > >> this. > > > > Yea, I already mentioned this. We could also stat the UPDATING > > file for the entry? Perhaps some kind of string could be checked > > with grep or something. > > UPDATING needs /src, which a) might not be available, and b) may be more > recent the the installed software. > -Oliver BLAH! The date from uname compaired to date of advisory. Shit, that only works for kernel. Hmmm -- Tom Rhodes