IETF Logo Mail Archive

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

Petr Špaček <pspacek@isc.org> Fri, 03 December 2021 09:01 UTC

Return-Path: <pspacek@isc.org>
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 A1B583A0CB0 for <dnsop@ietfa.amsl.com>; Fri, 3 Dec 2021 01:01:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.951
X-Spam-Level:
X-Spam-Status: No, score=-3.951 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, NICE_REPLY_A=-1.852, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isc.org header.b=pooXfDm5; dkim=pass (1024-bit key) header.d=isc.org header.b=NrWVF3R3
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 y0Xytlp3FPuR for <dnsop@ietfa.amsl.com>; Fri, 3 Dec 2021 01:01:52 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 057EA3A151A for <dnsop@ietf.org>; Fri, 3 Dec 2021 01:01:51 -0800 (PST)
Received: from zimbrang.isc.org (zimbrang.isc.org [149.20.1.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx.pao1.isc.org (Postfix) with ESMTPS id 80354433F2B for <dnsop@ietf.org>; Fri, 3 Dec 2021 09:01:50 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=isc.org; s=ostpay; t=1638522110; bh=T+59zSVxSaXn2rq2LZ8m9mHlFtf2jkaPVjM3w9gFMBA=; h=Date:Subject:To:References:From:In-Reply-To; b=pooXfDm5r2E03zPROyC1z/QKc29xH61JmUvzjJptCDfXDRC3v2ev9H2E1SrsftAwN +VrDAt7Qc1W5zb1mrPisNBWnsLpyc3zK31xfpYigHRIFT8upzGb3wdx0SHbcGKXnbw 044D7PV86BuZ330RSt4SauAAykmhXfKVAH/IIp88=
Received: from zimbrang.isc.org (localhost.localdomain [127.0.0.1]) by zimbrang.isc.org (Postfix) with ESMTPS id 78EABF26EDF for <dnsop@ietf.org>; Fri, 3 Dec 2021 09:01:50 +0000 (UTC)
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbrang.isc.org (Postfix) with ESMTP id 4FCBCF26EE0 for <dnsop@ietf.org>; Fri, 3 Dec 2021 09:01:50 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.10.3 zimbrang.isc.org 4FCBCF26EE0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=05DFB016-56A2-11EB-AEC0-15368D323330; t=1638522110; bh=T+59zSVxSaXn2rq2LZ8m9mHlFtf2jkaPVjM3w9gFMBA=; h=Message-ID:Date:MIME-Version:To:From; b=NrWVF3R3MXePIVXie3gNaOJSRRI1sxmQemVUrug6GPadMHzOYrEQqAeIaWTsJk4zA kXjgSkM8hVyOI/EiwVDJX7F9WLMAvBPB+fm/rmZez5pU9XRJaqhrSGYRoB+A2/tV2v 730CVtPrI21O2kSKFKKKTZi1znKdkT/ia9qo9RK8=
Received: from zimbrang.isc.org ([127.0.0.1]) by localhost (zimbrang.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id S_uki_gYfVQZ for <dnsop@ietf.org>; Fri, 3 Dec 2021 09:01:50 +0000 (UTC)
Received: from [192.168.0.157] (ip-86-49-254-49.net.upcbroadband.cz [86.49.254.49]) by zimbrang.isc.org (Postfix) with ESMTPSA id D9298F26EDF for <dnsop@ietf.org>; Fri, 3 Dec 2021 09:01:49 +0000 (UTC)
Message-ID: <5cf51ff5-8fd0-bfa9-5339-5e073527d6bf@isc.org>
Date: Fri, 03 Dec 2021 10:01:48 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.3.2
Content-Language: en-US
To: dnsop@ietf.org
References: <m1msK9b-0000HrC@stereo.hq.phicoh.net> <C3D5AC3A-CA5A-4F33-8BDA-DDFADD23649C@isc.org> <m1msN8S-0000HPC@stereo.hq.phicoh.net> <CADyWQ+FsS57YkN-fpqRdBSLMJGsCWyE4wdrENTUQw-ZFw+HXbA@mail.gmail.com>
From: Petr Špaček <pspacek@isc.org>
In-Reply-To: <CADyWQ+FsS57YkN-fpqRdBSLMJGsCWyE4wdrENTUQw-ZFw+HXbA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/lOH87EdI8l4u3--xypY7jn_pH3g>
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 09:01:57 -0000

On 01. 12. 21 12:07, Tim Wicinski wrote:
> 
> What I noticed in reading this nice write up was the warning image they 
> missed in the Route53 console
> because of the automation they use.  But most folks use 
> automation/tooling/etc in their workflow, and
> catching those warnings via automation is a bit tricky.
> 
> Right after this happened several different teams looking to sign their 
> zones got a little nervous.
> This writeup helps to show people how things can break, but also, there 
> is a great set of testing
> methods to assist others.
> 
> Mark's comments about adding tests in DNSVIZ would be pretty great.

It is already implemented in DNSViz since December 2020 (so a year+ 
before the Slack outage), but it is not shown by default:

https://github.com/dnsviz/dnsviz/issues/76#issuecomment-985331543

-- 
Petr Špaček

v2.23.0 | Report a Bug | By Email