From owner-freebsd-security@FreeBSD.ORG  Tue Jan 14 14:32:10 2014
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 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id CE6F4505;
 Tue, 14 Jan 2014 14:32:10 +0000 (UTC)
Received: from smtp.des.no (smtp.des.no [194.63.250.102])
 by mx1.freebsd.org (Postfix) with ESMTP id 8AD8B1ACD;
 Tue, 14 Jan 2014 14:32:10 +0000 (UTC)
Received: from nine.des.no (smtp.des.no [194.63.250.102])
 by smtp-int.des.no (Postfix) with ESMTP id CDEF67675;
 Tue, 14 Jan 2014 14:32:08 +0000 (UTC)
Received: by nine.des.no (Postfix, from userid 1001)
 id 65D4B3423D; Tue, 14 Jan 2014 15:32:05 +0100 (CET)
From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no>
To: Ferdinand Goldmann <ferdinand.goldmann@jku.at>
Subject: Re: NTP security hole CVE-2013-5211?
References: <B0F3AA0A-2D23-424B-8A79-817CD2EBB277@FreeBSD.org>
 <52CEAD69.6090000@grosbein.net>
 <81785015-5083-451C-AC0B-4333CE766618@FreeBSD.org>
 <52CF82C0.9040708@delphij.net>
 <CAO82ECEsS-rKq7A-9w7VuxKpe_c_f=tvZQoRKgHEfi-yPdNeGQ@mail.gmail.com>
 <86d2jud85v.fsf@nine.des.no>
 <97DABA91-0F6E-4109-992D-A3ADFE799018@jku.at>
Date: Tue, 14 Jan 2014 15:32:05 +0100
In-Reply-To: <97DABA91-0F6E-4109-992D-A3ADFE799018@jku.at> (Ferdinand
 Goldmann's message of "Tue, 14 Jan 2014 15:00:27 +0100")
Message-ID: <868uuibpne.fsf@nine.des.no>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-security@freebsd.org, Xin LI <d@delphij.net>,
 Palle Girgensohn <girgen@freebsd.org>
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.17
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, 14 Jan 2014 14:32:10 -0000

Ferdinand Goldmann <ferdinand.goldmann@jku.at> writes:
> Dag-Erling Sm=C3=B8rgrav <des@des.no> writes:
> > Doesn't "restrict noquery" block monlist in 4.2.6?
> I think it should be possible to block it using:
>
> disable monitor
>
> seems to work for me.

That disables monlist across the board, whereas the restrict mechanism
allows you to disable it selectively:

restrict default nomodify nopeer noquery notrap
restrict localhost

not quite as fine-grained, though, since "disable monitor" only disables
monlist while "restrict noquery" blocks all ntpq / ntpdc queries.

Of course, the default behavior for a sensible NTP implementation should
be to ignore everything except time queries.

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