From owner-freebsd-security Thu Jun 4 12:39:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19159 for freebsd-security-outgoing; Thu, 4 Jun 1998 12:39:09 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from alpha.sea-to-sky.net (sreid@sea-to-sky.net [204.244.200.240]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19141 for ; Thu, 4 Jun 1998 12:38:50 -0700 (PDT) (envelope-from sreid@alpha.sea-to-sky.net) Received: (from sreid@localhost) by alpha.sea-to-sky.net (8.8.7/8.8.7) id MAA22726; Thu, 4 Jun 1998 12:40:58 -0700 Date: Thu, 4 Jun 1998 19:40:57 +0000 ( ) From: Steve Reid To: freebsd-security@FreeBSD.ORG Subject: Advisory format nitpicking Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org How about putting real version numbers in these advisories? This "2.2.*" thing is only accurate until a new, fixed release appears. Looking over past advisories (to secure a freshly installed system) is a headache because _all_ the advisories say "Affects: FreeBSD 2.2.*". > Topic: security compromise via mmap > Category: core > Module: kernel > Announced: 1998-06-02 > Affects: FreeBSD 2.2.*, FreeBSD-stable before 1998/05/24 > and FreeBSD-current before 1998/05/19 suffer from > this problem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message