From owner-freebsd-security@FreeBSD.ORG  Wed May  1 03:00:59 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 45A5D128;
 Wed,  1 May 2013 03:00:59 +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 23A6C1394;
 Wed,  1 May 2013 03:00:58 +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 103C723F804;
 Tue, 30 Apr 2013 23:00:57 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.8.2 onyx.glenbarber.us 103C723F804
Authentication-Results: onyx.glenbarber.us; dkim=none
 reason="no signature"; dkim-adsp=none
Date: Tue, 30 Apr 2013 23:00:55 -0400
From: Glen Barber <gjb@FreeBSD.org>
To: Melanie Schulte <m-freebsd@fuglos.org>
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-13:05.nfsserver
Message-ID: <20130501030055.GF1579@glenbarber.us>
References: <201304292208.QAA16119@lariat.net>
 <20130430034603.GF1588@glenbarber.us>
 <201304300416.WAA20729@lariat.net>
 <20130430042415.GG1588@glenbarber.us>
 <CADLo839_J40E4O2s7Af3r1stH98B-fjKtBwmNovaPfY7peqi7Q@mail.gmail.com>
 <201304301936.NAA02519@lariat.net>
 <20130430211531.GA1621@glenbarber.us>
 <201304302241.QAA05359@lariat.net>
 <20130430224850.GA1579@glenbarber.us>
 <alpine.BSF.2.00.1305010443140.76122@m.fuglos.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature"; boundary="Zs/RYxT/hKAHzkfQ"
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.00.1305010443140.76122@m.fuglos.org>
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: Wed, 01 May 2013 03:00:59 -0000


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

On Wed, May 01, 2013 at 04:47:48AM +0200, Melanie Schulte wrote:
> Hi,
>=20
> >I disagree that there is a problem, however, since users building a
> >custom kernel should _not_ use freebsd-update(8) for kernel
> >upgrades.
>=20
> Could you please elaborate on that? I have also built my own kernel on
> my servers and I must have missed the section in the handbook saying
> that running a custom kernel implies that freebsd-update should not be
> used.
>=20
> Given a security problem, I don't want to spend hours recompiling my
> base system whereas freebsd-update fixed the problem in seconds.
>=20

freebsd-update(8) _always_ installs GENERIC.

Glen


--Zs/RYxT/hKAHzkfQ
Content-Type: application/pgp-signature

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

iQEcBAEBCAAGBQJRgIVnAAoJEFJPDDeguUaju+YH/2fAWKRQoJsHGcLHbhKnDIDG
LfXaCkVNxnMqAydrw+gS+wfZRKWi1Yg/lNoQt2gxP8xT8j2PSGEVriDI4j/GjwBt
pZ0ndT656kfE/OJGOQ8xAoU+5lGR8aSqdkQdk2puyBfRM78AC4jQ3AnJK+qkoaQO
PS49nFNOOSuQ047/hBitxA5RKYRgqzNbVHi5UA7NsF9f/FxfCz/5vpTTqO2Otel7
lnGhUDg0vsi1imS78lUYN2DprvRqbbWfsy89hK47khUTTh8y7BJSd9zR/w4d7H52
U5ndr6J+PC53NRHdN2Iyn8l9K8nAX511M0NFfb1gSUTsgDIt6CCLlsDo2Qtrxlk=
=g+ty
-----END PGP SIGNATURE-----

--Zs/RYxT/hKAHzkfQ--