From owner-freebsd-security@freebsd.org  Fri Apr 29 13:58:28 2016
Return-Path: <owner-freebsd-security@freebsd.org>
Delivered-To: freebsd-security@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77A59B1F0CD
 for <freebsd-security@mailman.ysv.freebsd.org>;
 Fri, 29 Apr 2016 13:58:28 +0000 (UTC)
 (envelope-from marquis@roble.com)
Received: from mx5.roble.com (mx5.roble.com [206.40.34.5])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mx5.roble.com", Issuer "mx5.roble.com" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 6E5851693
 for <freebsd-security@freebsd.org>; Fri, 29 Apr 2016 13:58:28 +0000 (UTC)
 (envelope-from marquis@roble.com)
Date: Fri, 29 Apr 2016 06:58:22 -0700 (PDT)
From: Roger Marquis <marquis@roble.com>
To: freebsd-security@freebsd.org
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-16:16.ntp
In-Reply-To: <1461929003.67736.2.camel@yandex.com>
References: <20160429082953.DB31D1769@freefall.freebsd.org>
 <9e6342a420259fec7bd21d6222cc6e05@zahemszky.hu>
 <1461929003.67736.2.camel@yandex.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Apr 2016 13:58:28 -0000

Despite the risk of beating a dead horse (apologies to non-native
english speakers for the acronym), as I cannot recall discussion of
migrating base, and since replacing ntpd with openntpd has been standard
practice in security-oriented environments for a few years now, perhaps
someone on the sec team could help me with this question:

What are the reasons FreeBSD has not deprecated ntpd in favor of
openntpd?

Roger


>> > 2) To update your vulnerable system via a binary patch:
>> > 
>> > Systems running a RELEASE version of FreeBSD on the i386 or amd64
>> > platforms can be updated via the freebsd-update(8) utility:
>> > 
>> > # freebsd-update fetch
>> > # freebsd-update install