From owner-freebsd-security@FreeBSD.ORG  Mon Feb  2 17:03:50 2004
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E559816A4CE
	for <freebsd-security@freebsd.org>;
	Mon,  2 Feb 2004 17:03:50 -0800 (PST)
Received: from obsecurity.dyndns.org
	(adsl-67-119-53-122.dsl.lsan03.pacbell.net [67.119.53.122])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8F91F43D45
	for <freebsd-security@freebsd.org>;
	Mon,  2 Feb 2004 17:03:49 -0800 (PST)
	(envelope-from kris@obsecurity.org)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id F358D66CD1; Mon,  2 Feb 2004 17:03:48 -0800 (PST)
Date: Mon, 2 Feb 2004 17:03:48 -0800
From: Kris Kennaway <kris@obsecurity.org>
To: Cy Schubert <Cy.Schubert@komquats.com>
Message-ID: <20040203010348.GA93989@xor.obsecurity.org>
References: <200401301607.i0UG7CIl082205@freefall.freebsd.org>
	<200402030029.i130Ts8F014698@cwsys.cwsent.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l"
Content-Disposition: inline
In-Reply-To: <200402030029.i130Ts8F014698@cwsys.cwsent.com>
User-Agent: Mutt/1.4.1i
cc: freebsd-security@freebsd.org
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-04:01.mksnap_ffs
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Security issues [members-only posting]
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>,
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Feb 2004 01:03:51 -0000


--XsQoSWH+UP9D9v3l
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 02, 2004 at 04:29:54PM -0800, Cy Schubert wrote:
> In message <200401301607.i0UG7CIl082205@freefall.freebsd.org>, FreeBSD=20
> Security
>  Advisories writes:
> > Branch                                                           Revisi=
on
> >   Path
> > -----------------------------------------------------------------------=
--
> > RELENG_5_1
> >   src/sbin/mksnap_ffs/mksnap_ffs.c                                1.2.2=
.1
> >   src/sys/conf/newvers.sh                                       1.50.2.=
14
> > RELENG_5_2
> >   src/sbin/mksnap_ffs/mksnap_ffs.c                                1.5.2=
.1
> >   src/sys/conf/newvers.sh                                        1.56.2=
.3
> > -----------------------------------------------------------------------=
--
>=20
> Would it be worth our while to list the revision in -CURRENT too (e.g. 1.=
7)?
>=20
> Just a thought.

It's explicitly stated on the Security webpage that -CURRENT isn't
supported by security advisories.

Kris

--XsQoSWH+UP9D9v3l
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFAHvN0Wry0BWjoQKURAlErAJ940ca/O3QLo6W0SbQPUQh3OWsyPgCg4ZCw
RPDVNMfyBCBIS3tEosn169g=
=DBsU
-----END PGP SIGNATURE-----

--XsQoSWH+UP9D9v3l--