Re: [DNSOP] How Slack didn't turn on DNSSEC

John Levine <johnl@taugh.com> Fri, 03 December 2021 02:41 UTC

Return-Path: <johnl@iecc.com>
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 E1B183A10C9 for <dnsop@ietfa.amsl.com>; Thu, 2 Dec 2021 18:41:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=LXSxJ56D; dkim=pass (2048-bit key) header.d=taugh.com header.b=DMGWrnxb
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 dS-reg2M_GLD for <dnsop@ietfa.amsl.com>; Thu, 2 Dec 2021 18:41:56 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 5CE623A098F for <dnsop@ietf.org>; Thu, 2 Dec 2021 18:41:56 -0800 (PST)
Received: (qmail 99960 invoked from network); 3 Dec 2021 02:41:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=18676.61a983ef.k2112; bh=X5Lu9W9GUYHGi57bdcYsNTKOm3Hq4MaxhRq7IbmH0lQ=; b=LXSxJ56D4SK0KNMKwLQKJVkIqxy7HdA8Jym2nFGRm4zGQUO8BG5/lbLSCFoRvJPPGn6awBhisRCRthyVzSPj0lu5SNUEPZVCBTwMgO5HF0d+DOlujXiFzqQPgujjfR5YN94cncm4MBpwVasiYzXP7k4Yg9dDmTgneUNZQIuKAciEi5nNCkdoXGsV6xhwQCJvFz/3OGzzYa80XnWQskgp1915u34xeHR5zlzcgT6VtDIbtfIiE5HJSBmPaESD+gC1/bhlC+j3+RzB8ux35jbxxtS3hmSA7R7WjlltmyFZA0aPtHdPvy8D3HzzEReEtuLTXKlNhjOGbsHBFdsrHAk1Aw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=18676.61a983ef.k2112; bh=X5Lu9W9GUYHGi57bdcYsNTKOm3Hq4MaxhRq7IbmH0lQ=; b=DMGWrnxbi17RIOos4x+qBi+ULtZtKnNC2PZYnpqU1UAuKPtCHjAJXOghXiCn3XESr0bNTNHyNIDEkXuM4+zZSZqqkbJzL7vioddnwYIwAGY1cvxS4cZ/62ioy7Qkavi605NFgnwNA/OEHOf1rB5wggvczfa4GgY1zSv1X4WrrczNkoTFspegPqE4uq0Z5nqh6/zOfNSyUBUMjFEsMEn7GU0Hp6kJmudXsIeOth9q4xDdXONnJM6iVfHMkKr5M09yprvxc1kaS+eNZTvyGWATvzg5JeAaxwN5q6kyJTfVFg7lGp9T1iiIWolhLLcbFgG9ERjMoXxlXP1ItiaveErpng==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 03 Dec 2021 02:41:51 -0000
Received: by ary.qy (Postfix, from userid 501) id 16DFA30E2F8E; Thu, 2 Dec 2021 21:41:49 -0500 (EST)
Date: Thu, 02 Dec 2021 21:41:49 -0500
Message-Id: <20211203024151.16DFA30E2F8E@ary.qy>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <321906C3-25B1-4E2C-B27D-DFA26EADC463@dukhovni.org>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/bguQ-rV3b32MR6apT_KXCu3dpIQ>
Subject: Re: [DNSOP] How Slack didn't turn on DNSSEC
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: Fri, 03 Dec 2021 02:42:00 -0000

It appears that Viktor Dukhovni  <dnsop@ietf.org> said:
>However, I do think that the skill level required need not always
>be or remain "wizard".  They had some bad luck running into a not
>fully baked stack on the provider end.

While they should have caught the apex CNAME, I can't really blame
them for not anticipating that AWS Route 53 would have buggy
DNSSEC handling.  Wildcards are unusual but they're not *that* unusual.

I realize the problem with test suites that the test suite tends to
become the de-facto spec, but it might be nice to come up with a list
of tests that check for famous bugs.

R's,
John