Re: Last Call: 'The Plain SASL Mechanism' to Proposed Standard

"Kurt D. Zeilenga" <Kurt@OpenLDAP.org> Wed, 23 February 2005 15:36 UTC

Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j1NFadsQ007984; Wed, 23 Feb 2005 07:36:39 -0800 (PST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j1NFadnZ007983; Wed, 23 Feb 2005 07:36:39 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from boole.openldap.org (root@boole.openldap.org [204.152.186.50]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j1NFadxr007976 for <ietf-sasl@imc.org>; Wed, 23 Feb 2005 07:36:39 -0800 (PST) (envelope-from Kurt@OpenLDAP.org)
Received: from gypsy.OpenLDAP.org (24-205-218-53.cs-cres.charterpipeline.net [24.205.218.53]) (authenticated bits=0) by boole.openldap.org (8.13.1/8.13.1) with ESMTP id j1NFXRNM024398 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Feb 2005 15:36:36 GMT (envelope-from Kurt@OpenLDAP.org)
Message-Id: <6.2.0.14.0.20050223072045.05c60580@mail.openldap.org>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Wed, 23 Feb 2005 07:32:42 -0800
To: Simon Josefsson <jas@extundo.com>
From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
Subject: Re: Last Call: 'The Plain SASL Mechanism' to Proposed Standard
Cc: Jeffrey Hutzelman <jhutz@cmu.edu>, iesg@ietf.org, ietf-sasl@imc.org, Sam Hartman <hartmans-ietf@mit.edu>
In-Reply-To: <iluzmxv62as.fsf@latte.josefsson.org>
References: <E1CziRz-0003w5-Hm@megatron.ietf.org> <ilu7jl0pulv.fsf@latte.josefsson.org> <6.2.0.14.0.20050222093430.05ec9e50@mail.openldap.org> <iluoeecmh8b.fsf@latte.josefsson.org> <tslis4kxo8i.fsf@cz.mit.edu> <ilufyzom9ee.fsf@latte.josefsson.org> <6CD8A044767E91A3E0B1271C@sirius.fac.cs.cmu.edu> <iluzmxv62as.fsf@latte.josefsson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

At 01:41 AM 2/23/2005, Simon Josefsson wrote:
>That view seem consistent, and now I understand it.  A further
>question then: Why are unassigned code points allowed in the input to
>DeriveAuthzid()? 

If SASLprep is used, then unassigned code points won't appear
in the input to DerivedAuthzid as such an authcid value
cannot possibly match any stored authcid value.  In the
pseudo-code, this is the case of FetchPasswordHash(pAuthcid)
returning NULL (unknown authcid).

Of course, if using another prepare algorithm the behavior
is implementation specific.

Kurt