From owner-freebsd-security@FreeBSD.ORG  Fri Jan  2 17:59:57 2015
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 35F7B20B
 for <freebsd-security@freebsd.org>; Fri,  2 Jan 2015 17:59:57 +0000 (UTC)
Received: from smtp.des.no (smtp.des.no [194.63.250.102])
 by mx1.freebsd.org (Postfix) with ESMTP id E891B666EA
 for <freebsd-security@freebsd.org>; Fri,  2 Jan 2015 17:59:56 +0000 (UTC)
Received: from nine.des.no (smtp.des.no [194.63.250.102])
 by smtp-int.des.no (Postfix) with ESMTP id 5B9F49DFA;
 Fri,  2 Jan 2015 17:59:52 +0000 (UTC)
Received: by nine.des.no (Postfix, from userid 1001)
 id B08485B65; Fri,  2 Jan 2015 18:59:49 +0100 (CET)
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To: Roger Marquis <marquis@roble.com>
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-14:31.ntp
References: <20141223233310.098C54BB6@nine.des.no>
 <86h9wln9nw.fsf@nine.des.no> <549A5492.6000503@grosbein.net>
 <868uhx43i5.fsf@nine.des.no> <20141226200838.DE83DACE@hub.freebsd.org>
 <8661cy9jim.fsf@nine.des.no> <20141231195427.AECE022B@hub.freebsd.org>
 <86y4plgjnm.fsf@nine.des.no>
Date: Fri, 02 Jan 2015 18:59:49 +0100
In-Reply-To: <86y4plgjnm.fsf@nine.des.no> ("Dag-Erling =?utf-8?Q?Sm=C3=B8r?=
 =?utf-8?Q?grav=22's?= message of
 "Fri, 02 Jan 2015 18:46:37 +0100")
Message-ID: <86tx09gj1m.fsf@nine.des.no>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-security@freebsd.org
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.18-1
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: Fri, 02 Jan 2015 17:59:57 -0000

Dag-Erling Sm=C3=B8rgrav <des@des.no> writes:
> $ sudo env UNAME_r=3DX.Y-RELEASE freebsd-update fetch install

Actually, you want to do this from *outside* the jail, partly out of
healthy paranoia and partly so freebsd-update will re-use previously
downloaded indexes and patches:

$ sudo env UNAME_r=3DX.Y-RELEASE freebsd-update -b /path/to/jail fetch inst=
all

Don't worry about conflicts - freebsd-update names its working directory
after the sha256 sum of the destination directory, so you can fetch,
merge, install and rollback updates for multiple jails as well as the
host independently of eachother.

DES
--=20
Dag-Erling Sm=C3=B8rgrav - des@des.no