From owner-freebsd-security@FreeBSD.ORG Tue Apr 30 04:24:18 2013 Return-Path: Delivered-To: freebsd-security@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B1B99833; Tue, 30 Apr 2013 04:24:18 +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 8FE7518C1; Tue, 30 Apr 2013 04:24:18 +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 E866823F804; Tue, 30 Apr 2013 00:24:16 -0400 (EDT) DKIM-Filter: OpenDKIM Filter v2.8.2 onyx.glenbarber.us E866823F804 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Tue, 30 Apr 2013 00:24:15 -0400 From: Glen Barber To: Brett Glass Subject: Re: FreeBSD Security Advisory FreeBSD-SA-13:05.nfsserver Message-ID: <20130430042415.GG1588@glenbarber.us> References: <201304292055.r3TKtcEs039958@freefall.freebsd.org> <201304292208.QAA16119@lariat.net> <20130430034603.GF1588@glenbarber.us> <201304300416.WAA20729@lariat.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="v2Uk6McLiE8OV1El" Content-Disposition: inline In-Reply-To: <201304300416.WAA20729@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\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2013 04:24:18 -0000 --v2Uk6McLiE8OV1El Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 29, 2013 at 10:16:43PM -0600, Brett Glass wrote: > At 09:46 PM 4/29/2013, Glen Barber wrote: >=20 > >This has _always_ been the case with freebsd-update(8). >=20 > Should it be? Yes. freebsd-update(8) does not, and cannot, know of custom kernel configurations. > It seems to me that the current behavior >=20 > a) Violates POLA; and >=20 Wrong. Users that build a custom kernel are responsible for maintaining the custom kernel for upgrades. > b) Puts any system with a custom kernel at serious risk if > surgery and/or a kernel rebuild is not done prior to the > next reboot. If there's a power failure, the system may > well not come up. Wrong. Previous statement applies. Glen --v2Uk6McLiE8OV1El Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJRf0dvAAoJEFJPDDeguUajoO8H/2lYpy4aXLNsROVGHxjYWCno N/D7HJHZ45DZgLCjXhTYAQ/AR+wiWQv9JAt7t6BAhnXJaK0MP2HgOcKSWlmjHjM3 29SkAh0RmTsQWDxtY5uTV8QCEEcQf31y/56n/gqSv6OS11aDy6jHLu1cCy6dSgHX aTqpHdTpmKL4qvzF4HhkRFqGiFOKVtHxPOfzFk/HZrMM3rTU/kfdkXhZhYrXJ0s0 Ib+PoNEOebTtqpGNYnb27EPKYIDhvYfRD/URdmaYVZj2oKZvL/+FqrVYQ2d3iX5Q XYguLfDcazg1j9/QdVxeDrKQ8XggRJtdrb+BHvCwrWLSUoyYn5BJOjqkdcPoUB0= =sWl3 -----END PGP SIGNATURE----- --v2Uk6McLiE8OV1El--