Re: [DNSOP] TSIG - BADKEY error handling appears to be underspecified.

Klaus Malorny <Klaus.Malorny@knipp.de> Mon, 17 September 2018 07:23 UTC

Return-Path: <Klaus.Malorny@knipp.de>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F6C1130DE3 for <dnsop@ietfa.amsl.com>; Mon, 17 Sep 2018 00:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
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 F8eR9wBADmmb for <dnsop@ietfa.amsl.com>; Mon, 17 Sep 2018 00:23:53 -0700 (PDT)
Received: from kmx5b.knipp.de (kmx5b.knipp.de [IPv6:2a01:5b0:0:29::6a]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9671F127133 for <dnsop@ietf.org>; Mon, 17 Sep 2018 00:23:53 -0700 (PDT)
Received: from hp9000.do.knipp.de (hp9000.do.knipp.de [195.253.2.54]) by kmx5b.knipp.de (Postfix) with ESMTP id E209D3005B4; Mon, 17 Sep 2018 07:23:51 +0000 (UTC)
Received: from [195.253.2.27] (mclane.do.knipp.de [195.253.2.27]) by hp9000.do.knipp.de (Postfix) with ESMTP id DA1FA7049F; Mon, 17 Sep 2018 09:23:51 +0200 (MESZ)
To: Mark Andrews <marka@isc.org>
Cc: dnsop WG <dnsop@ietf.org>
References: <A23114D1-75BE-4BA5-9C27-78B070BDBD3F@isc.org> <d3a331ac-b324-c53d-dac9-3f9cb1a8c139@knipp.de> <513BF18D-BAD4-4495-B9B4-293BEBEBBFA9@isc.org>
From: Klaus Malorny <Klaus.Malorny@knipp.de>
Message-ID: <6e5d4ed8-439a-83b4-af98-8e4b756fc1d2@knipp.de>
Date: Mon, 17 Sep 2018 09:23:43 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:64.0) Gecko/20100101 Thunderbird/64.0a1
MIME-Version: 1.0
In-Reply-To: <513BF18D-BAD4-4495-B9B4-293BEBEBBFA9@isc.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Spamd-Bar: /
Authentication-Results: kmx5b.knipp.de
X-Rspamd-Server: s671
X-Rspamd-Queue-Id: E209D3005B4
X-Spamd-Result: default: False [0.00 / 15.00]; IP_WHITELIST(0.00)[195.253.2.54]; NEURAL_HAM(-0.00)[-0.037,0]; ASN(0.00)[asn:8391, ipnet:195.253.0.0/16, country:DE]
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/wGcvagB7bOJIUqSWR3OVPiWIN8Q>
Subject: Re: [DNSOP] TSIG - BADKEY error handling appears to be underspecified.
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Sep 2018 07:23:55 -0000

On 17.09.18 02:27, Mark Andrews wrote:
> Actually having the clients time and fudge in those fields for BADKEY
> provides spoofing protection for the unsigned responses. This is especially
> important with opportunistic TSIG,which is what TSIG with a WKK will be, as
> there is no longer the presumption that server is configured for the key that
> there was when TSIG was originally drafted.  It’s all about getting answers
> through acceptance filters.
Hi Mark,

thanks for the explanation, this sounds reasonable, I will fix our software in 
the next release.

Regards,

Klaus