IETF Logo Mail Archive

Re: [DNSOP] DNSOP: question about hardening "something like mDNS" against attacks

Ted Lemon <mellon@fugue.com> Mon, 26 October 2020 20:09 UTC

Return-Path: <mellon@fugue.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 15F393A0EB3 for <dnsop@ietfa.amsl.com>; Mon, 26 Oct 2020 13:09:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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 (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 t9A1_p5d0fzc for <dnsop@ietfa.amsl.com>; Mon, 26 Oct 2020 13:09:44 -0700 (PDT)
Received: from mail-qv1-xf41.google.com (mail-qv1-xf41.google.com [IPv6:2607:f8b0:4864:20::f41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FBBC3A0EA9 for <dnsop@ietf.org>; Mon, 26 Oct 2020 13:09:44 -0700 (PDT)
Received: by mail-qv1-xf41.google.com with SMTP id w9so4959580qvj.0 for <dnsop@ietf.org>; Mon, 26 Oct 2020 13:09:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=yW4euwvtFD/o1271RDtqZuEJyWRxSYjCf8FZvuwwZ2g=; b=RNBEKSztwJ63XkmYzDZWQW69/tGqnnwqjwD7qNUeN7F5Lmo7N4mK1SqrJOj5+igxVw Kks47Btf8UO9orKnwmRiJkXKpHw9U8PfsrAZtJo9imXn7BC0t46MpbiO3C0A6Zn0jx+A +c8Ad9WCavWGzYG+R1UdmAG2Ehn4M5waWQKSENYsFLKRDWL0RapVGqKlrt/PKmTBgiGP M6rXK5106nI5xiKwDHHOotskgjFXDcr9oIgJKSzH0M/TbxM6CbA8F1kbUIdtt0ogbEYt YFWzg2SU5XAbo24/v+/Z9FuiwJlxMzUbZZLtIF4HBcbi5x1q4ShN+itnLxow7r4/dQxa xrSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=yW4euwvtFD/o1271RDtqZuEJyWRxSYjCf8FZvuwwZ2g=; b=EjAAhTeWubT6JDHfE82qonOGvf2V5OVzT+cpG5S/kpTffe+uBWQjRB1A7nNhppfT7p W/fkBCzei0jW9eVqgeqS9sBBOMGiqt5nKecqsK5CXsOGJolg/qjHTIPltGZnfYWIrkOg 7FhEd6jXLhjKTQOrolAC4S6TVmAfT49n7i+8yeUXA2FeSP0QN1WGRNS7OGl9nxLiWHfH CUHIeQWh3useHYCBqqZnnJl5SqonMkxODU+c+akHOs/p2SC15mTu1rKUoBualCJmBFRG 4c52D+YZNRY05cKyoNUXLGwF1ib8b1gVkrSb9/P6DblgSw1iHaW0vHgkISk0LkOtLsjy 54Cw==
X-Gm-Message-State: AOAM53366jXRugPBbI3h/XEUKVhfk2uHEX51eHU/oWA8tsCJPNfIOVEx 9d8oKWFwoTjPZNA7KEVuFbYv+U01p6PB4w==
X-Google-Smtp-Source: ABdhPJwWdelgsZ2rTlPs3DqoWzEftZLa0lelPnJgTQo2eYSjnJlMXkZnXW3OxEO8RfhQ0BqFpmEVBQ==
X-Received: by 2002:ad4:58eb:: with SMTP id di11mr18604519qvb.56.1603742983305; Mon, 26 Oct 2020 13:09:43 -0700 (PDT)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.ma.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id 11sm7266794qkc.91.2020.10.26.13.09.42 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Oct 2020 13:09:42 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <4EBB9789-EDA8-418F-898F-3A2D0B3C5CC2@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E40B93C3-E43C-48D3-BA8A-8A18DE9093CC"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.0.3.2.91\))
Date: Mon, 26 Oct 2020 16:09:41 -0400
In-Reply-To: <20201026200538.GA1328776@puck.nether.net>
Cc: Toerless Eckert <tte@cs.fau.de>, dnsop <dnsop@ietf.org>, kaduk@mit.edu
To: Jared Mauch <jared@puck.nether.net>
References: <20201025192456.GG48111@faui48f.informatik.uni-erlangen.de> <539093D8-97C4-448F-A9C4-288C2586BC51@fugue.com> <20201026165915.GA40654@faui48f.informatik.uni-erlangen.de> <41920477-8979-49EC-9F14-11A100D622FF@fugue.com> <6D931ED7-7A34-4E9D-B2CC-D2F555D79E0B@puck.nether.net> <20201026174221.GC40654@faui48f.informatik.uni-erlangen.de> <20201026200538.GA1328776@puck.nether.net>
X-Mailer: Apple Mail (2.3654.0.3.2.91)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/vD129VUEoziw5n0BKhRp1qyC3g0>
Subject: Re: [DNSOP] DNSOP: question about hardening "something like mDNS" against attacks
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, 26 Oct 2020 20:09:46 -0000

On Oct 26, 2020, at 4:05 PM, Jared Mauch <jared@puck.nether.net> wrote:
>> If the anwer of the experts is "do not harden implementations of existing protocols",
>> but only improve protocols or eliminate security risks from underlays, i think
>> that is not a good strategy to show to implementors trying to understand how
>> to best harden existing protocols, but i will happily take that guidance
>> and remove the text about the suggested heuristics.

The point of my answer was not “don’t do anything to harden it,” but rather “don’t do _that_.”  :)

v2.20.0 | Report a Bug | By Email