IETF Logo Mail Archive

Re: [Captive-portals] Requirements for "captive portal closed" notifications

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 21 March 2018 13:33 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: captive-portals@ietfa.amsl.com
Delivered-To: captive-portals@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE77712DA4A for <captive-portals@ietfa.amsl.com>; Wed, 21 Mar 2018 06:33:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.435
X-Spam-Level: *
X-Spam-Status: No, score=1.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_SBL_CSS=3.335, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 kyZMDgyCgUl6 for <captive-portals@ietfa.amsl.com>; Wed, 21 Mar 2018 06:33:36 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B0DB12DA27 for <captive-portals@ietf.org>; Wed, 21 Mar 2018 06:33:36 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:67c:370:128:a11:96ff:fe01:81e0]) by relay.sandelman.ca (Postfix) with ESMTPS id A83031F95A for <captive-portals@ietf.org>; Wed, 21 Mar 2018 13:33:34 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 32802874; Wed, 21 Mar 2018 13:14:04 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: captive-portals@ietf.org
In-reply-to: <CAKD1Yr0oDZQJQ1n899Vtm1VPwwV2ZaLZTJV19a35G6pHf0x1Dg@mail.gmail.com>
References: <CAKD1Yr3rP24jQ6sMpoXZ3pU02FmvwDNc9=w2oAh4bMWZmEtQ_A@mail.gmail.com> <CADo9JyXpW-rn81kwOkqx8+=iBMTWd+x1FoMm-YTCm+Efmb23gQ@mail.gmail.com> <CAKD1Yr0oDZQJQ1n899Vtm1VPwwV2ZaLZTJV19a35G6pHf0x1Dg@mail.gmail.com>
Comments: In-reply-to Lorenzo Colitti <lorenzo@google.com> message dated "Tue, 20 Mar 2018 16:01:44 +0000."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Wed, 21 Mar 2018 13:14:04 +0000
Message-ID: <16033.1521638044@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/captive-portals/Cj5F-Dp5JpAnapdrjeWDOTlCEP8>
Subject: Re: [Captive-portals] Requirements for "captive portal closed" notifications
X-BeenThere: captive-portals@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussion of issues related to captive portals <captive-portals.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/captive-portals>, <mailto:captive-portals-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/captive-portals/>
List-Post: <mailto:captive-portals@ietf.org>
List-Help: <mailto:captive-portals-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/captive-portals>, <mailto:captive-portals-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2018 13:33:38 -0000

Lorenzo Colitti <lorenzo@google.com> wrote:
    david>     Is there any data that shows ICMP (and its insecurity) being used
    david> for off-path attacks like this today? Networks (as they do today) may
    david> just filter out ICMP they don't support from the edge.


    > Regardless of whether this is happening today, it seems unwise to
    > propose something with an obvious security hole like this. The risk is
    > that we do a bunch of work and then security review tells us "?REDO
    > FROM START".  

We have secdir secretary Tero on the list now...

Even if offpath attacks are challenging, given typical coffee shop wifi,
on-path attacks are trivial.

The ICMP is a hint.  That's also good for many reasons involving rate
limiting and idempotency.

(Sorry I missed the WG session. IASA2 was more important)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email