Re: [kitten] Fwd: New Version Notification for draft-howard-gss-sanon-00.txt

Simon Josefsson <simon@josefsson.org> Sat, 04 April 2020 11:19 UTC

Return-Path: <simon@josefsson.org>
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 E894F3A09F7 for <kitten@ietfa.amsl.com>; Sat, 4 Apr 2020 04:19:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=josefsson.org
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 SpciGxRYOznW for <kitten@ietfa.amsl.com>; Sat, 4 Apr 2020 04:19:03 -0700 (PDT)
Received: from duva.sjd.se (duva.sjd.se [IPv6:2001:9b1:8633::105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 868C83A09F9 for <kitten@ietf.org>; Sat, 4 Apr 2020 04:19:03 -0700 (PDT)
Received: from latte (31-208-42-58.cust.bredband2.com [31.208.42.58]) (authenticated bits=0) by duva.sjd.se (8.15.2/8.15.2/Debian-8) with ESMTPSA id 034BIie5018676 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 4 Apr 2020 11:18:46 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=josefsson.org; s=default; t=1585999126; bh=uL+u1E7Mj4T+gJj2QotKDHrzyX7Zmf+yL+7dl27nrpY=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=ez3qocKzEXXmy3erDb+b4axm/lxWcF3jKO+5f0OqTgNt6FJtMg8ysC28Fca2SdNvE h/5cXSp6xem8b28+DLMxPimh0+zvhGQIYpRrib00Y1tp9Q2mlIDVi3lvu9HGl6c06/ HEYKuV13jPc0o8mQK2QDGQB1RNbAaEf9faAumnS36Vd6XkBjVxtquMj4MC7uelCKp4 0P3ddjt+sy26j5puFIPRFz/MExrnPQrRngJ+lVFo/V/zRbanIxZRMJMNPIR+e9QpdA L2VjCcxzPSVcuponCnyLBbVZ9/bxLJeYwWKhUYIwxrJa0HbAYMXSHNhRXauLhEIf6N iKRvQ2yblZkNg==
From: Simon Josefsson <simon@josefsson.org>
To: Luke Howard <lukeh=40padl.com@dmarc.ietf.org>
Cc: "kitten@ietf.org" <kitten@ietf.org>
References: <158562149038.11496.7234948048087895644@ietfa.amsl.com> <03F73286-C983-44C6-B10D-7E826AE2C609@padl.com>
OpenPGP: id=B1D2BD1375BECB784CF4F8C4D73CF638C53C06BE; url=https://josefsson.org/key-20190320.txt
X-Hashcash: 1:22:200404:kitten@ietf.org::kqPTXWcv3Tw1ChLP:MQP
X-Hashcash: 1:22:200404:lukeh=40padl.com@dmarc.ietf.org::+XwmZndVecDzDnsK:O8Sa
Date: Sat, 04 Apr 2020 13:18:44 +0200
In-Reply-To: <03F73286-C983-44C6-B10D-7E826AE2C609@padl.com> (Luke Howard's message of "Tue, 31 Mar 2020 13:28:11 +1100")
Message-ID: <87pncnbisr.fsf@latte.josefsson.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
X-Virus-Scanned: clamav-milter 0.102.2 at duva.sjd.se
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/2xzsP09SGCPBTXustFnhCojiQ_E>
Subject: Re: [kitten] Fwd: New Version Notification for draft-howard-gss-sanon-00.txt
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 04 Apr 2020 11:19:07 -0000

Luke Howard <lukeh=40padl.com@dmarc.ietf.org> writes:

> Hi everybody,
>
> Below is a specification for a simple anonymous mechanism based on
> curve25519 that does not authenticate either initiator or acceptor.

Interesting!  When would this be useful in SASL?  GS2 requires that the
mechanism supports mutual authentication, so while I definitely see
value in having this as a GSS-API mechanism I don't understand when it
would provide value for a SASL application, and how it would actually
work in GS2.

/Simon