From owner-freebsd-security@FreeBSD.ORG  Tue Apr 30 03:46:07 2013
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 56A7F1AC;
 Tue, 30 Apr 2013 03:46:07 +0000 (UTC) (envelope-from gjb@FreeBSD.org)
Received: from onyx.glenbarber.us (onyx.glenbarber.us [199.48.134.227])
 by mx1.freebsd.org (Postfix) with ESMTP id 381BB1799;
 Tue, 30 Apr 2013 03:46:06 +0000 (UTC)
Received: from glenbarber.us (kaos.glenbarber.us [71.224.221.174])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate) (Authenticated sender: gjb)
 by onyx.glenbarber.us (Postfix) with ESMTPSA id 5C32B23F804;
 Mon, 29 Apr 2013 23:46:05 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.8.2 onyx.glenbarber.us 5C32B23F804
Authentication-Results: onyx.glenbarber.us; dkim=none
 reason="no signature"; dkim-adsp=none
Date: Mon, 29 Apr 2013 23:46:03 -0400
From: Glen Barber <gjb@FreeBSD.org>
To: Brett Glass <brett@lariat.net>
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-13:05.nfsserver
Message-ID: <20130430034603.GF1588@glenbarber.us>
References: <201304292055.r3TKtcEs039958@freefall.freebsd.org>
 <201304292208.QAA16119@lariat.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature"; boundary="NY6JkbSqL3W9mApi"
Content-Disposition: inline
In-Reply-To: <201304292208.QAA16119@lariat.net>
X-Operating-System: FreeBSD 10.0-CURRENT amd64
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: freebsd-security@freebsd.org
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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, 30 Apr 2013 03:46:07 -0000


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

On Mon, Apr 29, 2013 at 04:08:22PM -0600, Brett Glass wrote:
> Please be advised that, when using freebsd-update(8) to install the patch=
 for
> this security problem, freebsd-update will move the current kernel to /bo=
ot/kernel.old,
> and install a new GENERIC kernel in /boot/kernel, even if you have built =
a custom
> kernel and created a copy of the GENERIC kernel in /boot/GENERIC.=20
>=20
> The kernel in /boot/GENERIC is NOT updated, nor are the modules in that d=
irectory
> updated. What's more, if you did not build modules for your custom kernel=
, you
> will not get copies of the updated NFS modules.
>=20
> This is probably not the behavior most users who have built custom kernel=
s will
> want or expect. (I would have hoped that the GENERIC kernel, its modules,=
 and the
> kernel sources would be updated and that I'd be reminded to rebuild my cu=
stom kernel
> if necessary.)
>=20

This has _always_ been the case with freebsd-update(8).

Glen


--NY6JkbSqL3W9mApi
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQEcBAEBCAAGBQJRfz57AAoJEFJPDDeguUaj6ZgH/1eBAaIrofVAo304Zr220ADN
KUB2z0ez+qJaxrahu3T89I4F/ZkxCu4FoKWgWiiFPBnOPRZpAfF1lL3NypB7rb+5
Z6m4a9pXmYzOS7LadqKvO3GdVEmRp633k6jf7A1Bb72jIeLiHsi+87gZ995l/NLZ
LphfN8TS77K5tkOXc6AQeq6PnY5Yu8Ap+inxeQaX4REjHirnYMy6q7a5fkfpknlY
TF+pw9PU8eVWJEHWo3/3Z2oDk6ymGFkZQW/Op4yEHvWfItMWihHAH1FYj2dt8quA
D5BWH4FQCfr+8N9w2NO+xRi1/moGEzNHhEKiPiiO/BjYc51Crs/EOiJ0HJQKcEM=
=JyQZ
-----END PGP SIGNATURE-----

--NY6JkbSqL3W9mApi--