Re: [Ntp] I-D Action: draft-ietf-ntp-alternative-port-01.txt
Miroslav Lichvar <mlichvar@redhat.com> Wed, 17 February 2021 12:39 UTC
Return-Path: <mlichvar@redhat.com>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C7F93A19B2 for <ntp@ietfa.amsl.com>; Wed, 17 Feb 2021 04:39:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.668
X-Spam-Level:
X-Spam-Status: No, score=-2.668 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.57, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xOW9PG4CLK4u for <ntp@ietfa.amsl.com>; Wed, 17 Feb 2021 04:39:36 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFD1F3A19AE for <ntp@ietf.org>; Wed, 17 Feb 2021 04:39:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1613565574; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=nx4FZA4g96HttVPHnqTiSvW+YYWzT/hJCtJzzLLBrAo=; b=AJa176ERsXRIq+7Oyp8bNl5NJKIX714t8kQf7jeE//sSbvcizpMb8bboCklQ9NPoAR7McB /paftpjqxwUTM0VyDGS3D9yCOnEbr4IxAFub0SgE9gtR/dSZcGBgyLxHzjagkVPC22231p Rgoht2HqNSZPZrmu5/RuM8YBhmyCy5Q=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-27-n6yAic15P1KPkWv1bnxZFg-1; Wed, 17 Feb 2021 07:39:33 -0500
X-MC-Unique: n6yAic15P1KPkWv1bnxZFg-1
Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 1BF37107ACC7; Wed, 17 Feb 2021 12:39:32 +0000 (UTC)
Received: from localhost (holly.tpb.lab.eng.brq.redhat.com [10.43.134.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 712AB10023B0; Wed, 17 Feb 2021 12:39:31 +0000 (UTC)
Date: Wed, 17 Feb 2021 13:39:29 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Hal Murray <hmurray@megapathdsl.net>
Cc: ntp@ietf.org
Message-ID: <YC0OgSYl/LDeImdI@localhost>
References: <161340151392.27073.10527818098176839039@ietfa.amsl.com> <20210217120124.9606940605C@ip-64-139-1-69.sjc.megapath.net>
MIME-Version: 1.0
In-Reply-To: <20210217120124.9606940605C@ip-64-139-1-69.sjc.megapath.net>
X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22
Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/uyvrxjwsa3rCbUqUeFHwnd8a0xo>
Subject: Re: [Ntp] I-D Action: draft-ietf-ntp-alternative-port-01.txt
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Feb 2021 12:39:37 -0000
On Wed, Feb 17, 2021 at 04:01:24AM -0800, Hal Murray wrote: > Looks good. > > Do we need to include rate limiting? > > Without rate limiting, an NTP server can be used as a reflector. I'm not > plugged into the crowd that does the anti-DoS work. How much of a problem is > a non-amplifying reflector? I don't think it's a significant problem. At least I have not heard about any attacks using a 1:1 NTP reflection. It seems there are many other protocols (e.g. ICMP) that have this property and are not rate limited by default. Rate limiting is not a good security mechanism. As you point out, attackers can avoid it by using a large number of addresses. With IPv6 there is practically an infinite number of them for the attackers to use. Rate limiting in NTP is a security issue on its own. It can be exploited by attackers to deny or degrade the service to legitimate clients of the server. I think this is a bigger issue than the reflection. -- Miroslav Lichvar
- [Ntp] I-D Action: draft-ietf-ntp-alternative-port… internet-drafts
- Re: [Ntp] I-D Action: draft-ietf-ntp-alternative-… Hal Murray
- Re: [Ntp] I-D Action: draft-ietf-ntp-alternative-… Miroslav Lichvar