Re: [Emu] Issue 47 Certificate identity checks

Eliot Lear <lear@cisco.com> Mon, 12 April 2021 13:02 UTC

Return-Path: <lear@cisco.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 9C4513A1CB0 for <emu@ietfa.amsl.com>; Mon, 12 Apr 2021 06:02:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.597
X-Spam-Level:
X-Spam-Status: No, score=-9.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 Fwdpw_0WG-8O for <emu@ietfa.amsl.com>; Mon, 12 Apr 2021 06:02:50 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 551463A1CF2 for <emu@ietf.org>; Mon, 12 Apr 2021 06:02:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4874; q=dns/txt; s=iport; t=1618232570; x=1619442170; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=k9LPk4XgnzE7sfTgWRzmXkZUu2SkKqgCInpNEXReeDw=; b=GwpBzOMaMTFdd1dVh9x+J1XJ9mLzkFDoMGynUwBFZqkOQ/HwdLuSfDf5 1LGfAx4TYlRF1S13wz5WBhcEqE7E2MAJcXnyZqtTVOBTS6DRwcIWLlo4j kd8HUPMJMEkVDHozevvJ5UiC2zZKra2w2bfyTEonHtQUHBlgpu79szxXW A=;
X-Files: signature.asc : 488
X-IPAS-Result: A0BTAABPRHRglxbLJq1RCRsBAQEBAQEBAQUBAQESAQEBAwMBAQGCEoEjglUBJxIxhEKJBIgwKId6jEuIIAQHAQEBCgMBATQEAQGEUAKBeSY4EwIDAQEBAwIDAQEBAQEFAQEBAgEGBBQBAQEBAQEBAWiFXYZEAQEBAQIBI1YFCwsEFCoCAlcGE4JxAYJmIasyd4EygQGEWIRiEIE5gVOFKgGGT0OCC4ETJwwQgjAvPoQWFIMvNYIrBIJFgVygHZ0CgxWDPoFFl3kEH5QrkEa0PAGEAQIEBgUCFoFrIYFbMxoIGxVlAYI+PhIZDo44jjI/Ay84AgYBCQEBAwmKTi2CFgEB
IronPort-HdrOrdr: A9a23:d7jVj6Hji1itzV+UpLqEaseALOonbusQ8zAX/mp6ICYlEfCwvc aogfgdyFvImC8cMUtNpfmsMLSNKEm8ybdb+o8UVI3JYCDHvy+SIJhm/c/exVTbexHW0uJGz6 9vf+xfBbTLYGRSqcb/7E2GH807wN+BmZrGuc7kw31gTR5nZshbhm8TNi+hHkJ7XwVAD5Yifa Dsg/ZvnSaqengcc62AaEUtYu6rnayoqLvWJToPBxsq82C1/FeVwY+/NQSE1REDVD4K5rEu/Q H+4mrEz5Tmle2nwRnB0GKW1bBqoZ/Kz9tOA9HksLlzFgnR
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.82,216,1613433600"; d="asc'?scan'208,217";a="34972500"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 12 Apr 2021 13:02:48 +0000
Received: from [10.61.144.80] ([10.61.144.80]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 13CD2lUf016449 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 12 Apr 2021 13:02:48 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <BEE48F72-7167-47C8-B4C6-7A486E2A05A0@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_CD05CA03-F344-4ABB-BBAA-E832BEFD141D"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
Date: Mon, 12 Apr 2021 15:02:46 +0200
In-Reply-To: <CE04DDF5-2605-4C2D-9E95-6C1DEDA478B8@deployingradius.com>
Cc: Joseph Salowey <joe@salowey.net>, EMU WG <emu@ietf.org>
To: Alan DeKok <aland@deployingradius.com>
References: <CAOgPGoArm2RdEN4V-L9XEUvOeG0Vs+58Zj_p3Y2yRY0aYsVV_A@mail.gmail.com> <98456329-CE85-4BB2-B93F-74776FEBA299@cisco.com> <CE04DDF5-2605-4C2D-9E95-6C1DEDA478B8@deployingradius.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
X-Outbound-SMTP-Client: 10.61.144.80, [10.61.144.80]
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/-eDGk6e8c5um6hIT9hpnMBKz7Zo>
Subject: Re: [Emu] Issue 47 Certificate identity checks
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, 12 Apr 2021 13:02:57 -0000

Hi Alan,

> On 12 Apr 2021, at 14:52, Alan DeKok <aland@deployingradius.com> wrote:
> 
>>> 
>>> EAP TLS peer implementations MUST allow for configuration of a unique trust root to validate the server's certificate.
>> 
>> This statement seems independent of the previous one, and may be overly broad.  Let me give you an example: a device may be designed only to operate as part of a federation.
> 
>  I would agure there that the federation should have it's own CA.

That’s what I’m thinking.  But I could imagine hardcoded devices that make use of it.  That’s all.

Eliot