From owner-freebsd-security@FreeBSD.ORG  Tue Apr 30 04:16:49 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 DBF236E0;
 Tue, 30 Apr 2013 04:16:49 +0000 (UTC)
 (envelope-from brett@lariat.net)
Received: from lariat.net (lariat.net [66.62.230.51])
 by mx1.freebsd.org (Postfix) with ESMTP id 7394D1887;
 Tue, 30 Apr 2013 04:16:49 +0000 (UTC)
Received: from Toshi.lariat.net (IDENT:ppp1000.lariat.net@lariat.net
 [66.119.58.2] (may be forged))
 by lariat.net (8.9.3/8.9.3) with ESMTP id WAA20729;
 Mon, 29 Apr 2013 22:16:45 -0600 (MDT)
Message-Id: <201304300416.WAA20729@lariat.net>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 29 Apr 2013 22:16:43 -0600
To: Glen Barber <gjb@FreeBSD.org>
From: Brett Glass <brett@lariat.net>
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-13:05.nfsserver
In-Reply-To: <20130430034603.GF1588@glenbarber.us>
References: <201304292055.r3TKtcEs039958@freefall.freebsd.org>
 <201304292208.QAA16119@lariat.net>
 <20130430034603.GF1588@glenbarber.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Tue, 30 Apr 2013 11:20:40 +0000
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 04:16:49 -0000

At 09:46 PM 4/29/2013, Glen Barber wrote:

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

Should it be? It seems to me that the current behavior

a) Violates POLA; and

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.

--Brett Glass