IETF Logo Mail Archive

Re: [homenet] webauthn for routers

Ted Lemon <mellon@fugue.com> Thu, 13 June 2019 15:47 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0F80120147 for <homenet@ietfa.amsl.com>; Thu, 13 Jun 2019 08:47:29 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 iNS45ImTOQ0f for <homenet@ietfa.amsl.com>; Thu, 13 Jun 2019 08:47:27 -0700 (PDT)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 67D641202EA for <homenet@ietf.org>; Thu, 13 Jun 2019 08:47:27 -0700 (PDT)
Received: by mail-qt1-x82b.google.com with SMTP id j19so23078954qtr.12 for <homenet@ietf.org>; Thu, 13 Jun 2019 08:47:27 -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=b2BVSxm4KOtm8RLv5+F5sD/V6HM4+uH2BI7GE9+6wyY=; b=sMPZtvyg0Fwb0ItzLb1G0PoDFPU1d1OH1FvZjcCOwZwZt5cHllLBL6kHym3MR1tQWz tF2kV8q6hPnT8L0JW7Jd7+KAln8A5JJ+L7Yl+gt8ughrQLuodZHoim+UaC2bErm6rPnG PrH3g6MHiWdDlEDfe/QHI+zbpmQfA+U4TDUadaDzNKWr295wiNucjrTu1DlsFKbZDmNY hA5pO2dxJLOjxQcC/ew0zyXfsLLlIst2AvS3uH7jh4l7iwpaa478LVUZASpuN9Zk5YbT THkZOlJofekgjL/XXNIMAVmQgZ6vMp0dPHZvM3ISOJk2+7UcNDOK35nXpVkIpSiupzYv cz/g==
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=b2BVSxm4KOtm8RLv5+F5sD/V6HM4+uH2BI7GE9+6wyY=; b=NaHQINt1swEvCrq+zl1ftXsxIRDcBpnbPhplU1vcaNJxpo3G0F34wPy24UmtdGeFt9 SV8Lrfq315yz+LD5f5akMZFEEUrqt+Cw+T9oTTN2q0RLM4Rgc3f8aavASTenqwFDICy4 PhFPeXxJia5mZRQmPUK19W+P5h6RPkDH2ShtfIw3r5brEbAtXHqynVC4/wDNUnEODS9N g34TQHnCGZPR1jwjRhWZNZ3Qxt7jgRTH4VfDTxjBtL5e0PB4Vz3KIjms+JjRNY4zDWoK fiK4OQgyLmG/94T5UpbT4fIhvhq4soRgcKYNR1ZEqmV82Ni2dnk9u8nkC/7pVNyyqMfs Cf+g==
X-Gm-Message-State: APjAAAXhAdNDrtGl2woYRgJimfnESrwkYydFFQndjCGno7S7GCnvosxP GxSDPIcscEli6NZCCwsWpKlWDg==
X-Google-Smtp-Source: APXvYqxqJWKFzx31zjagep2NkYlN9H7pE63CPZF88c+XefjjsDXw2uhXHYzwz1d/QjHpbsMemMRtpw==
X-Received: by 2002:a0c:9891:: with SMTP id f17mr1233078qvd.49.1560440846474; Thu, 13 Jun 2019 08:47:26 -0700 (PDT)
Received: from [192.168.8.100] (c-73-186-137-119.hsd1.ma.comcast.net. [73.186.137.119]) by smtp.gmail.com with ESMTPSA id w16sm22797qtc.41.2019.06.13.08.47.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Jun 2019 08:47:25 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <496DBED4-24E6-49FE-B9D3-C2BFC7ACEE98@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8D248C6F-2BF5-4A42-8F46-B14D6DAA6073"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Thu, 13 Jun 2019 11:47:24 -0400
In-Reply-To: <cde3329b-cc06-b4eb-5d87-cf74f21368ea@fresheez.com>
Cc: Michael Richardson <mcr@sandelman.ca>, homenet@ietf.org
To: Michael Thomas <mike@fresheez.com>
References: <CADZyTkkgd8f49V+yoZvPZXx3b-_YRzpgUY1-obroq9QMLnFWNw@mail.gmail.com> <878su8fj24.wl-jch@irif.fr> <2348.1560261275@localhost> <87ftofwqut.wl-jch@irif.fr> <27503.1560302791@localhost> <87ef3zwoew.wl-jch@irif.fr> <4109.1560349340@localhost> <EC7FDA4F-1859-4B35-A8AC-D33E1A96F979@fugue.com> <ff7f2700-3862-59bd-abfb-22589562bddb@mtcc.com> <20218.1560366783@localhost> <288a310b-3b99-748d-74ce-a878ff43ee77@fresheez.com> <6179.1560377924@localhost> <604b4062-f2c5-30af-73ff-2e97b7541a9b@fresheez.com> <30470.1560435490@localhost> <cde3329b-cc06-b4eb-5d87-cf74f21368ea@fresheez.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/MHSh59F0Renj0E4w1kxWNrBClng>
Subject: Re: [homenet] webauthn for routers
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Jun 2019 15:47:30 -0000

On Jun 13, 2019, at 11:15 AM, Michael Thomas <mike@fresheez.com> wrote:
> All of which require authentication of some form, which the router itself doesn't have the credentials. But home routers do have a few different characteristics: proximity and local addressing. Maybe your work you pointed out might be applicable?

“how you are connected” plus “no conflict” is a fairy effective ad-hoc method for establishing trust.

E.g., for a very long time, ISPs have used the fact that you are connected to their network as a basis for authorizing your DHCP transaction.   If the ISP is doing the front-end naming, then that mechanism could work here as well.   If someone else is doing front-end naming, then you probably have to have put a credit card in somewhere…

v2.23.0 | Report a Bug | By Email