IETF Logo Mail Archive

Re: [Emu] Best practices for supplicants and authenticators

Alan DeKok <aland@deployingradius.com> Mon, 18 November 2019 15:57 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 0057112099C for <emu@ietfa.amsl.com>; Mon, 18 Nov 2019 07:57:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 n9cYJOBZMSdZ for <emu@ietfa.amsl.com>; Mon, 18 Nov 2019 07:57:22 -0800 (PST)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88C4C120994 for <emu@ietf.org>; Mon, 18 Nov 2019 07:57:22 -0800 (PST)
Received: from [192.168.46.58] (24-52-251-6.cable.teksavvy.com [24.52.251.6]) by mail.networkradius.com (Postfix) with ESMTPSA id 043965F1; Mon, 18 Nov 2019 15:57:20 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none header.from=deployingradius.com
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <AT5PR8401MB053007BCE574F9DD75DBF5CDDB4D0@AT5PR8401MB0530.NAMPRD84.PROD.OUTLOOK.COM>
Date: Mon, 18 Nov 2019 10:57:19 -0500
Cc: EMU WG <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1DCB7146-EAE5-4450-A690-0783F687DF72@deployingradius.com>
References: <526166D8-80B9-4356-84D9-52ACD49E004B@deployingradius.com> <AT5PR8401MB0530EEE33628E2DB3098C1E6DB4D0@AT5PR8401MB0530.NAMPRD84.PROD.OUTLOOK.COM> <D3569D77-A2AB-4FEE-BF2A-1AAAFCB9D3D6@deployingradius.com> <AT5PR8401MB05309AD8F339DF5B6BD2E993DB4D0@AT5PR8401MB0530.NAMPRD84.PROD.OUTLOOK.COM> <4D4ACE1D-B565-4AB2-87B8-FD8362A0E76F@deployingradius.com> <AT5PR8401MB053007BCE574F9DD75DBF5CDDB4D0@AT5PR8401MB0530.NAMPRD84.PROD.OUTLOOK.COM>
To: "Cappalli, Tim (Aruba)" <timc@hpe.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/7R0YslHSTkNfrgyuCZkyrCp8-tI>
Subject: Re: [Emu] Best practices for supplicants and authenticators
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: Mon, 18 Nov 2019 15:57:24 -0000


> On Nov 18, 2019, at 10:47 AM, Cappalli, Tim (Aruba) <timc@hpe.com> wrote:
> 
> Alan – Adding yet another OID and/or EKU to a certificate does not change the fact that no authority can attest to that information. A public CA cannot validate a ownership of an NAIRealm. 

  That's not true.

  Public CAs validate ownership of domain names. The NAIRealm is a domain name.  And, the NAIRealm is the *same* as the domain name in the certificate.  Which the CA validated.

  Unless you have a counter-argument, that discussion should be closed.

> So while a supplicant could be configured to validate that the server’s NAIRealm matches the local configuration, that doesn’t change the requirement to manually configure the supplicant.

  I explained how it could simplify the supplicants configuration.

> So what are we actually trying to improve here?

  See my previous messages for explanations.

  Alan DeKok.

v2.23.0 | Report a Bug | By Email