IETF Logo Mail Archive

Re: [Emu] Idea: New X509 Extension for securing EAP-TLS

Alan DeKok <aland@deployingradius.com> Sun, 10 November 2019 22: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 247A41200F1 for <emu@ietfa.amsl.com>; Sun, 10 Nov 2019 14:57:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 Zdek5miMPX1d for <emu@ietfa.amsl.com>; Sun, 10 Nov 2019 14:57:24 -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 DACDB1200E0 for <emu@ietf.org>; Sun, 10 Nov 2019 14:57:23 -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 99A94564; Sun, 10 Nov 2019 22:57:21 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none header.from=deployingradius.com
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <E0B8DAA7-8C7C-455F-B5BE-128670A093D3@vigilsec.com>
Date: Sun, 10 Nov 2019 17:57:19 -0500
Cc: Jan-Frederik Rieckers <rieckers@uni-bremen.de>, emu@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <BD30A64D-539C-422D-9413-880AF8D6A16F@deployingradius.com>
References: <102dd850-b1ae-3426-8189-45876b7b419d@uni-bremen.de> <04E2AEF5-F1EE-4B74-B5BB-DFE099543C92@vigilsec.com> <D735A4DB-1CFB-4DF4-ACB7-BC6EFDBC6CDE@deployingradius.com> <E0B8DAA7-8C7C-455F-B5BE-128670A093D3@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/qKa1f0ng2GZAKMbC2f4wG2iBAf4>
Subject: Re: [Emu] Idea: New X509 Extension for securing EAP-TLS
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: Sun, 10 Nov 2019 22:57:26 -0000

On Nov 10, 2019, at 11:16 AM, Russ Housley <housley@vigilsec.com> wrote:
> Thanks for the overview.  It was very helpful.

  Glad to help.

> RFC 7586 define the NAIRealm as an otherName in the SubjectAltName of a certificate.  It seems that the NAIRealm name form works equally well, regardless of the role that the certificate holder is performing in the protocol.

  I agree.

  TBH, I like this proposal for securing EAP-TLS.  It may take time to deploy, but adding more clarity to certificates is always useful.  I'd be in favour of WG adoption of a document based on this.

  FWIW, a configuration file that creates certificates with the NAIRealm is located here:

https://github.com/FreeRADIUS/freeradius-server/blob/master/raddb/certs/server.cnf

  Alan DeKok.

v2.23.0 | Report a Bug | By Email