IETF Logo Mail Archive

Re: [Emu] Provisioning, configuration, etc. and EAP

Alan DeKok <aland@deployingradius.com> Tue, 29 March 2022 18:25 UTC

Return-Path: <aland@deployingradius.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 534AF3A1B6E for <emu@ietfa.amsl.com>; Tue, 29 Mar 2022 11:25:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham 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 O7jGce11czwF for <emu@ietfa.amsl.com>; Tue, 29 Mar 2022 11:25:18 -0700 (PDT)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88A9F3A1B68 for <emu@ietf.org>; Tue, 29 Mar 2022 11:25:18 -0700 (PDT)
Received: from smtpclient.apple (24-52-251-6.cable.teksavvy.com [24.52.251.6]) by mail.networkradius.com (Postfix) with ESMTPSA id C0982211; Tue, 29 Mar 2022 18:25:14 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none) header.from=deployingradius.com
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <25502.1648572805@localhost>
Date: Tue, 29 Mar 2022 14:25:13 -0400
Cc: EMU WG <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <115B22A9-BAB1-48EC-A0E0-0C34886F7455@deployingradius.com>
References: <8C03CE4A-B987-4962-9AA3-5DF8FB32ECB5@deployingradius.com> <69280.1648310501@dooku> <BC205D3A-DCDD-4C43-AF88-9031622FCAFA@deployingradius.com> <94640.1648472403@dooku> <501558C4-7829-4144-8966-52B79358367E@deployingradius.com> <25502.1648572805@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/RaxrcovhK0XheMyQSW-zUy9paTw>
Subject: Re: [Emu] Provisioning, configuration, etc. and EAP
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Mar 2022 18:25:24 -0000

On Mar 29, 2022, at 12:53 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
>>  Use the normal SSID.  Unauthenticated EAP-TLS.  User ID of
>> "provisioning@eap.arpa".
> 
> But that could be even worse in many settings!
> To do this safely means setting up layer-2 isolation for the device so that
> it can't talk to (or attack) any other device (nor be attacked).
> 
> Or do you have some other idea on how to support this?

  Layer 2 isolation is the main one.

  There's also the realization that modern access devices are fairly powerful, and many contain walled gardens / captive portals.  It shouldn't be difficult to extend that functionality with basic provisioning methods based on DNS / web.  Which the systems already have.

  Alan DeKok.

v2.23.0 | Report a Bug | By Email