IETF Logo Mail Archive

Re: [Emu] draft-ietf-emu-rfc7170bis-03.txt and password length

Alan DeKok <aland@deployingradius.com> Fri, 27 January 2023 14:01 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 68670C14CEE5 for <emu@ietfa.amsl.com>; Fri, 27 Jan 2023 06:01:36 -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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ME7yw8mjtWDW for <emu@ietfa.amsl.com>; Fri, 27 Jan 2023 06:01:32 -0800 (PST)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC33EC14F749 for <emu@ietf.org>; Fri, 27 Jan 2023 06:01:31 -0800 (PST)
Received: from smtpclient.apple (135-23-95-173.cpe.pppoe.ca [135.23.95.173]) by mail.networkradius.com (Postfix) with ESMTPSA id DFC1119A; Fri, 27 Jan 2023 14:01:29 +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 16.0 \(3696.120.41.1.1\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <CAA7Lko-qKqpBLnU2gP4Pos-Y1F48+mxYU06y-0etrw6uRMZMVQ@mail.gmail.com>
Date: Fri, 27 Jan 2023 09:01:28 -0500
Cc: EMU WG <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B49287CF-0398-4FF0-8FAA-0EC5C7DA27F2@deployingradius.com>
References: <9A85E1BF-4CBF-4D3F-98F9-A07D496F7759@deployingradius.com> <DB6PR0701MB304746750BFA21068CB8B23489CE9@DB6PR0701MB3047.eurprd07.prod.outlook.com> <CAA7Lko8=kJnqpB-YNFVTs=E0mpCrcOsEpRePvwkGp-h8dDdw9g@mail.gmail.com> <159d378b-06f4-cf12-edc1-41dcbcf67541@lear.ch> <CAA7Lko-qKqpBLnU2gP4Pos-Y1F48+mxYU06y-0etrw6uRMZMVQ@mail.gmail.com>
To: Heikki Vatiainen <hvn@radiatorsoftware.com>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/dTPsmYpXWiiD5bOJKSk3-_liSMY>
Subject: Re: [Emu] draft-ietf-emu-rfc7170bis-03.txt and password length
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 27 Jan 2023 14:01:36 -0000

On Jan 27, 2023, at 7:56 AM, Heikki Vatiainen <hvn@radiatorsoftware.com> wrote:
> My understanding is that the "housekeeping" functionality, or any
> other variation of multi-round inner password authentication, means
> that Basic-Password-Auth-Req <-->  Basic-Password-Auth-Resp exchange
> is done multiple times before a single inner password authentication
> method is considered completed and an Intermediate-Result TLV and
> Crypto-Binding TLV are needed. I'll need to check the previous
> discussion about filler Intermediate-Result and CB.

  The discussion was that every inner authentication required an Intermediate-Result-TLV, and a Crypto-Binding TLV.

> When strictly reading the RFC and draft, it doesn't talk about
> multi-round inner password authentication, but I guess this is
> supported?

  It mentions multiple rounds of password authentication.  I'll add text on permitting use-cases like "password + OTP" as separate rounds.

  It may be worth noting that multiple rounds of EAP are supported for different Identity-Types, i.e. machine and then user.  I don't think we want to allow multiple EAP authentications for a particular user.

  Alan DeKok.

v2.23.0 | Report a Bug | By Email