From owner-freebsd-vuxml@FreeBSD.ORG Tue Aug 17 18:27:30 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 CF00716A579; Tue, 17 Aug 2004 18:27:29 +0000 (GMT) Received: from gw.celabo.org (gw.celabo.org [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67B8943D4C; Tue, 17 Aug 2004 18:27:29 +0000 (GMT) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (not verified)) by gw.celabo.org (Postfix) with ESMTP id 073DA5486E; Tue, 17 Aug 2004 13:27:29 -0500 (CDT) Received: by madman.celabo.org (Postfix, from userid 1001) id 795A86D452; Tue, 17 Aug 2004 13:27:19 -0500 (CDT) Date: Tue, 17 Aug 2004 13:27:19 -0500 From: "Jacques A. Vidrine" To: Oliver Eikemeier Message-ID: <20040817182719.GB46244@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Oliver Eikemeier , Tom Rhodes , freebsd-vuxml@FreeBSD.org References: <20040817175847.GC43426@madman.celabo.org> <0569BE5A-F07B-11D8-924A-00039312D914@fillmore-labs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0569BE5A-F07B-11D8-924A-00039312D914@fillmore-labs.com> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.6i cc: freebsd-vuxml@FreeBSD.org cc: Tom Rhodes 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 18:27:30 -0000 On Tue, Aug 17, 2004 at 08:26:56PM +0200, Oliver Eikemeier wrote: > epoch 0? 1970-01-01? Or the date vuxml was announced? This would be > easier to find than XXX, especially in a rendered version. Or just leave > the entry empty. > > Any constant will do, it could be easily rendered to `unknown'. I find a > non-constant value (date of entry) a bad choice it is more difficult to > test against (and could be correct). Yes, you are right, we just need a constant string like 'unknown' or 'unspecified'. > >By way of example, I've been using FreeBSD 4.7-RELEASE-p1 == 4.7_1. I'm > >not entirely satisfied and I am open to suggestions. This part has been > >ill-specified. :-( > > Ehm, __FreeBSD_version? What's bad with that? Documented in the Porters > Handbook, and to find out. __FreeBSD_version is for developers, not users. Users need to see actual release numbers. Cheers, -- Jacques Vidrine / nectar@celabo.org / jvidrine@verio.net / nectar@freebsd.org