[OPSAWG] Asserting Wireless Network Connections Using DNS Revolvers' Identities
Dan Wing <danwing@gmail.com> Thu, 22 September 2022 17:12 UTC
Return-Path: <danwing@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2053C1522D6; Thu, 22 Sep 2022 10:12:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TWMAljF_NQUR; Thu, 22 Sep 2022 10:12:35 -0700 (PDT)
Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70FEBC14CF0F; Thu, 22 Sep 2022 10:12:35 -0700 (PDT)
Received: by mail-pg1-x52f.google.com with SMTP id u69so9779234pgd.2; Thu, 22 Sep 2022 10:12:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:cc:message-id:date:subject:mime-version:reply-to :content-transfer-encoding:from:from:to:cc:subject:date; bh=xrDqqNitrGrH5KQhNdrpfkRD7V/l50fyVHuXaWEuwo4=; b=HR0L8KOj8ovviAHq++iW6hN0IDtHmcuE67lP4oUDcQ8RueIuc9Fd3ukxD57tpETzLO YUIGho/Zy9AlE4Ijlxn+EG2f4Sv31EC9a8C1jQLP+az2BcwYoteo3kozn0WI405xmVgb NoeSmtdyAMI1Fmk+obA3OXB0ZV70r73l/yFnDe1d9RdMPNYvCheGyg49CLWA6taz40wF 9nftzDlWDLjh1+mfjaAeesa0oI32hs60le94E27oVxbwZmQgDujPAS1vT+XPRL6zga8H yMOYp+lgPKhXJm7FYZdunSY+Ja/J3H1t+M6uVKLH1hoZj3anT6pnrfGyXPoenBc+QupS oeqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:cc:message-id:date:subject:mime-version:reply-to :content-transfer-encoding:from:x-gm-message-state:from:to:cc :subject:date; bh=xrDqqNitrGrH5KQhNdrpfkRD7V/l50fyVHuXaWEuwo4=; b=HjlgHmqPLwZYnyE0UXdFz3W9Ne9/iOf9xpQyMlxwNp/xISsthb4VM/1u0+Ac4kr6Hp QPUd/mvzZFApj6+0FpifQLc2Rn5hBEE3Pz5de06BVMnMaccq2ReSEQb94PTbO0xTIpGT SS8mOUAOlDf+HaFYXiIzP6rt/iOKfq2w01G4uKsrgfe8MNE+yoKGoI/ndsDq3dwINkLS RMTyEZVIhk+2+Q88ObYDX+Zsm6Twa9vwu9ZbISWOfY7064DcsbfNIPJFeirwt1EaUqWF cozzdRASfQwa6gGAkJbsunlkVrbUY+HkNnJ1FnNdMf0BjLgjG/cKyQNIjddh4x59YJEU Pvbg==
X-Gm-Message-State: ACrzQf3iLriITAnViPrijnVA75qlV7CxLsq2AMMKek/EpsehcwE3WpdV VFNzf9lR0ERgK66ce0c0aKM4UD0KbP0=
X-Google-Smtp-Source: AMsMyM4kLovmj+KajNBNCNPNI45cFLsCXsEg2pB4K4nWsUeO3XH6xNzkBtgIN/6WaHqqvLF1vOsfvg==
X-Received: by 2002:a05:6a00:8c8:b0:52c:887d:fa25 with SMTP id s8-20020a056a0008c800b0052c887dfa25mr4682545pfu.86.1663866754405; Thu, 22 Sep 2022 10:12:34 -0700 (PDT)
Received: from smtpclient.apple ([47.208.218.46]) by smtp.gmail.com with ESMTPSA id h5-20020a170902680500b00178b717a0a3sm4351496plk.69.2022.09.22.10.12.33 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Sep 2022 10:12:33 -0700 (PDT)
From: Dan Wing <danwing@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Reply-To: "opsawg@ietf.org" <opsawg@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Date: Thu, 22 Sep 2022 10:12:31 -0700
Message-Id: <6D8FF242-44C4-4C72-9D46-354E7AA4BC29@gmail.com>
To: "secdispatch@ietf.org" <secdispatch@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/6BI5WnWe8A2MrOuuxNi23RX5zrg>
Subject: [OPSAWG] Asserting Wireless Network Connections Using DNS Revolvers' Identities
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Sep 2022 17:12:36 -0000
Secdispatch, opsawg, Based on earlier comments from Paul Wouters and Tommy Pauly, Tiru and I wrote Asserting Wireless Network Connections Using DNS Revolvers' Identities, https://datatracker.ietf.org/doc/html/draft-wing-opsawg-authenticating-network-00 Abstract: This document describes how a host uses the encrypted DNS server identity to reduce an attacker's capabilities if the attacker is emulating a wireless network. We are interested in feedback on points such as - considering attack vectors, are TOFU and extension to QR sufficient or should just require SSID to match FQDN of resolver's identity - is the mechanism worthwhile enough for clients and WiFi operators considering the amount of protection/assurance versus, say, 802.1X -Dan and Tiru
- [OPSAWG] Asserting Wireless Network Connections U… Dan Wing
- Re: [OPSAWG] [Secdispatch] Asserting Wireless Net… Kathleen Moriarty