From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 21:18:33 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B97C16A41C for ; Fri, 10 Jun 2005 21:18:33 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 088A943D1F for ; Fri, 10 Jun 2005 21:18:33 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1F84C51243; Fri, 10 Jun 2005 17:18:31 -0400 (EDT) Date: Fri, 10 Jun 2005 17:18:31 -0400 From: Kris Kennaway To: Stephen Montgomery-Smith , Steven Hartland , kama , freebsd-stable Message-ID: <20050610211830.GA64347@xor.obsecurity.org> References: <20050610170707.T66195@ns1.as.pvp.se> <01fe01c56dd3$9fa11bf0$b3db87d4@multiplay.co.uk> <42A9F2DB.8050600@math.missouri.edu> <20050610211425.GA33107@falcon.midgard.homeip.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DocE+STaALJfprDB" Content-Disposition: inline In-Reply-To: <20050610211425.GA33107@falcon.midgard.homeip.net> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: 5.4 not running HTT X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 21:18:33 -0000 --DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 10, 2005 at 11:14:25PM +0200, Erik Trulsson wrote: > On Fri, Jun 10, 2005 at 03:06:51PM -0500, Stephen Montgomery-Smith wrote: > > Steven Hartland wrote: > > >Have a read /usr/src/UPDATING it explains. > > > > >=20 > > It should be in /usr/src/UPDATING, but I don't see it there myself. >=20 > It depends on which version you are looking at the source of.=20 > In the release/security branches (RELENG_5_4, etc.) all security > patches (like this one) are noted in UPDATING. For the development > branches (RELENG_5 , -CURRENT) security patches usually don't get > mentioned. >=20 > I.e. if you are looking at the source for RELENG_5_4 there is a notice > in UPDATING, if you are looking at the source for RELENG_5 there is > not. In this particular case there probably should have been a note > added to UPDATING for both -STABLE and -CURRENT, but there wasn't. send-pr with the patch and/or talk to the security team. Kris --DocE+STaALJfprDB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCqgOmWry0BWjoQKURAmqeAJ9m5QmiWqDDoFpO+qsAuj76yNP3dQCfTlbm J+l4Lgzs155xJK+fC4c+7Nk= =J8KL -----END PGP SIGNATURE----- --DocE+STaALJfprDB--