From owner-freebsd-security@FreeBSD.ORG Wed May 1 02:22:36 2013 Return-Path: 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 77B5F8EA; Wed, 1 May 2013 02:22:36 +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 024CA128F; Wed, 1 May 2013 02:22:36 +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 9FF8623F804; Tue, 30 Apr 2013 22:22:30 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.8.2 onyx.glenbarber.us 9FF8623F804 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Tue, 30 Apr 2013 22:22:28 -0400 From: Glen Barber To: Brett Glass Subject: Re: FreeBSD Security Advisory FreeBSD-SA-13:05.nfsserver Message-ID: <20130501022228.GD1579@glenbarber.us> References: <201304292208.QAA16119@lariat.net> <20130430034603.GF1588@glenbarber.us> <201304300416.WAA20729@lariat.net> <20130430042415.GG1588@glenbarber.us> <201304301936.NAA02519@lariat.net> <20130430211531.GA1621@glenbarber.us> <201304302241.QAA05359@lariat.net> <20130430224850.GA1579@glenbarber.us> <201305010149.TAA07809@lariat.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="mJm6k4Vb/yFcL9ZU" Content-Disposition: inline In-Reply-To: <201305010149.TAA07809@lariat.net> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-security@FreeBSD.org, Colin Percival , Chris Rees X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 May 2013 02:22:36 -0000 --mJm6k4Vb/yFcL9ZU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 30, 2013 at 07:48:50PM -0600, Brett Glass wrote: > At 04:48 PM 4/30/2013, Glen Barber wrote: >=20 > >So, since I know you're not new to FreeBSD, if you feel there is a bug > >somewhere, please file a PR. I disagree that there is a problem, > >however, since users building a custom kernel should _not_ use > >freebsd-update(8) for kernel upgrades. > > >=20 > I will do that. BTW, I do not use freebsd-update(8) to update the kernel.= But > I do need it to update the kernel sources (so I can rebuild the kernel my= self) > and the userland sources and binaries. After all, I can't rebuild the wor= ld > on every production server each time there's a security fix to apply. >=20 Maybe I am missing the fundamental usage of freebsd-update(8). How does using freebsd-update(8) to fetch src/ updates install a new kernel? Pardon my ignorance here - I do not use freebsd-update(8) for any of my systems. Glen --mJm6k4Vb/yFcL9ZU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJRgHxkAAoJEFJPDDeguUajpsoIAICSoDiDTEgUeeeaND3W9CpN ywkYn5i19qg4Z9m10NWAG+H/JvqRWa2iw9lfgHytpC+TKhmMJnkin6/17DxXlBPB JFvD65Y/r5uepukjkvegZk+lA0e2L9dJ2ozilNn+CBFm+Kc0Wz6hUax5nWDI6xvr J2P5aEjoPiRNRgfI6Kh5VOKiGrpK+YpPAD97u6Lvoo9GSuiMjrQ3YALD4+TRcdzC 3ZCXKR+RtTCJRvMs/bKxes/QVYmm97HeTd8/Vy7619QaYKqRbdpZNiWXJNN4/1y+ EURgQpAkMrn8DduHcKZ01yn8oR16WM7PQ3DVCu7rp6oGIPH04uAlF5nI5sL/h08= =l5I1 -----END PGP SIGNATURE----- --mJm6k4Vb/yFcL9ZU--