IETF Logo Mail Archive

Re: [kitten] The Hashed-Token SASL Mechanism (SASL-HT)

Florian Schmaus <flo@geekplace.eu> Wed, 18 October 2017 06:55 UTC

Return-Path: <fschmaus@gmail.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2FBF132026 for <kitten@ietfa.amsl.com>; Tue, 17 Oct 2017 23:55:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level:
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Qfrnr1wjPchD for <kitten@ietfa.amsl.com>; Tue, 17 Oct 2017 23:55:02 -0700 (PDT)
Received: from mail-wm0-f42.google.com (mail-wm0-f42.google.com [74.125.82.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DF35127517 for <kitten@ietf.org>; Tue, 17 Oct 2017 23:55:02 -0700 (PDT)
Received: by mail-wm0-f42.google.com with SMTP id t69so7906195wmt.2 for <kitten@ietf.org>; Tue, 17 Oct 2017 23:55:02 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=+5XRV0EIXnL75NhHVV3zDKEcSnStxbHM2ECvskWUaZA=; b=rRrMjIEqyGNGWM2SwbWtXlXCjvQv8CDbbuVseJkqiwpFb1P3Jqzeow8u7tWT+xiSTB Q7CepNHB1snIq+wgWYUsBpgLmrJc+s1HarYhITmdXTVe6OvDFaHvKB7hr+hfFKSnddW/ FOm0tk/RhYbkRjLn90oKn/wDJtzc4ZILwBcrHuxV8hgigElOmTjyxXhPiFUghTTxmdYB GkrgxA12F93Om56Lk76F9cJiRlgzrzLk6SIec+rBqpf7Zhhs/WxIyozoDl6PS5md8CDn /DlX90W3B1IATIql0OnI3EKavMSe4L594JcTbD9xnM4Riq1D3M0Zpn0ACQMN7IWB6z7P v6YQ==
X-Gm-Message-State: AMCzsaW4oRWC4rPBFhjyolMQ9RcjlkIlnLWlOlZqtR8ge20+OtxSCGGt +s2ioUn1IDP570WsQvaUifim9XBI
X-Google-Smtp-Source: AOwi7QDkL6iGm8a9vk6glJPZAwb/OSks/pEZze+kZx4KgMxyYmUA/Am95QrSvWeBsiu4UA1q7x2iAQ==
X-Received: by 10.80.215.91 with SMTP id i27mr20691731edj.274.1508309700520; Tue, 17 Oct 2017 23:55:00 -0700 (PDT)
Received: from [192.168.43.144] (x59cc870d.dyn.telefonica.de. [89.204.135.13]) by smtp.googlemail.com with ESMTPSA id e56sm8608832edb.72.2017.10.17.23.54.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Oct 2017 23:54:58 -0700 (PDT)
To: kitten@ietf.org
References: <9913d71b-ae22-cc48-34b8-fb29fdf9a00c@geekplace.eu> <1508249331.3526135.1141665400.36944376@webmail.messagingengine.com> <7425e2f8-89a4-8a2d-8957-b640b8d97883@isode.com>
From: Florian Schmaus <flo@geekplace.eu>
Message-ID: <fceddb46-277f-af09-d0af-3fdd8ff2e3d6@geekplace.eu>
Date: Wed, 18 Oct 2017 08:54:50 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <7425e2f8-89a4-8a2d-8957-b640b8d97883@isode.com>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="Q0VLp1ngBpvKichwIb7fo8bFUCBge10Re"
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/83v9LedCcAu-ncdaFijNDG-x8GM>
Subject: Re: [kitten] The Hashed-Token SASL Mechanism (SASL-HT)
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Oct 2017 06:55:04 -0000

On 17.10.2017 18:57, Alexey Melnikov wrote:
> Hi Sam,
> 
> On 17/10/2017 15:08, Sam Whited wrote:
> 
>> On Fri, Sep 29, 2017, at 04:08, Florian Schmaus wrote:
>>> I would like to note the existence of draft-schmaus-kitten-sasl-ht-01:
>>>
>>> https://tools.ietf.org/html/draft-schmaus-kitten-sasl-ht-01
>> After a quick read through of the latest draft, the only thing I found
>> which I wasn't sure about was the following:
>>
>>> Before sending the authentication identity string the initiator SHOULD
>>> prepare the data with the UsernameCaseMapped profile of [RFC7613].
>> This limits the SASL mechanisms usefulness to Unicode encodings.
> I think use of Unicode, in particular UTF-8 is the right thing. Other
> character sets can be mapped to UTF-8.
> 
> Normalization to disallow problematic characters is a good thing, so I
> think a SHOULD level requirement is appropriate. But I am not sure that
> case-mapped version of UserName profile is the right thing here.

Good point. Since SASLprep also preserves the case, I switched to
UsernameCasePreserved in 02-SNAPSHOT.

- Florian

v2.23.0 | Report a Bug | By Email