Re: [kitten] SASL, how to choose the type of channel binding?

Rick van Rein <rick@openfortress.nl> Thu, 09 April 2020 13:30 UTC

Return-Path: <rick@openfortress.nl>
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 C5A7B3A09E3 for <kitten@ietfa.amsl.com>; Thu, 9 Apr 2020 06:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level:
X-Spam-Status: No, score=-2.119 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=openfortress.nl
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 Sd0iqXH0sZLu for <kitten@ietfa.amsl.com>; Thu, 9 Apr 2020 06:30:47 -0700 (PDT)
Received: from lb1-smtp-cloud9.xs4all.net (lb1-smtp-cloud9.xs4all.net [194.109.24.22]) (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 CDA473A098C for <kitten@ietf.org>; Thu, 9 Apr 2020 06:30:46 -0700 (PDT)
Received: from popmini.vanrein.org ([IPv6:2001:980:93a5:1::7]) by smtp-cloud9.xs4all.net with ESMTP id MXGVjGLrOZJ1DMXGWjv3r1; Thu, 09 Apr 2020 15:30:44 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=openfortress.nl; i=rick@openfortress.nl; q=dns/txt; s=fame; t=1586439043; h=message-id : date : from : mime-version : to : subject : references : in-reply-to : content-type : content-transfer-encoding : date : from : subject; bh=MhMDWMJCMyFuq0BuhJVq+0TAiZcy6N06AgVVPOx/G4E=; b=PQyApO/mDkL04gvR3dntmrF/FzURdMipqlWBE9x/lD538NdS3ImykMgN +LEY7XftnpWllFPrX1rwD3KjCf/HgJwl4I7fXu0nHUPPgttvvaJ3ZpC3ml zXqbKZKJaltq2l4iVYVxERxe6BuUnG8+B3vAZZoeZDw9Dcbfmy4iwYTrg=
Received: by fame.vanrein.org (Postfix, from userid 1006) id 7F1BF3959B; Thu, 9 Apr 2020 13:30:43 +0000 (UTC)
X-Original-To: kitten@ietf.org
Received: from airhead.local (phantom.vanrein.org [83.161.146.46]) by fame.vanrein.org (Postfix) with ESMTPA id 5DDED39597; Thu, 9 Apr 2020 13:30:43 +0000 (UTC)
Message-ID: <5E8F2382.2070804@openfortress.nl>
Date: Thu, 09 Apr 2020 15:30:42 +0200
From: Rick van Rein <rick@openfortress.nl>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: "kitten@ietf.org" <kitten@ietf.org>
References: <5E8F1ED9.1020108@openfortress.nl>
In-Reply-To: <5E8F1ED9.1020108@openfortress.nl>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bogosity: Unsure, tests=bogofilter, spamicity=0.520000, version=1.2.4
X-CMAE-Envelope: MS4wfLbnthS5ckQR0UhCScyS+N8Q46qOyxeorOJFkTarsSkQxaZmacErxqouCx3qCVTaALI9Vqw15ogsVjxtgxaieTaH+6ubSJnR/N/L1bvaWo3CEweOnsoP PyI6Rx6SXbIXQPOwV8vzzfyQkUHXEycMo+JvRzJCIt/DRs8a5NS8Rcu7+NUbFPoh8Wy6gTXzfHemBQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/mx2iiSNpfTcfpYaGUix5yhFkCNI>
Subject: Re: [kitten] SASL, how to choose the type of channel binding?
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: Thu, 09 Apr 2020 13:30:49 -0000

Oops,

I was blinded... have been focussing on the three forms, overlooking that there is a value after "p".

    gs2-cb-flag     = ("p=" cb-name) / "n" / "y"
                      ;; GS2 channel binding (CB) flag
                      ;; "p" -> client supports and used CB
                      ;; "n" -> client does not support CB
                      ;; "y" -> client supports CB, thinks the server
                      ;;           does not

Sorry :)
 -Rick