IETF Logo Mail Archive

Re: [kitten] SCRAM and draft-ietf-kitten-tls-channel-bindings-for-tls13

Sam Whited <sam@samwhited.com> Thu, 25 March 2021 12:11 UTC

Return-Path: <sam@samwhited.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 6B5423A1F78 for <kitten@ietfa.amsl.com>; Thu, 25 Mar 2021 05:11:13 -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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=samwhited.com header.b=eBcSAAos; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=TZb7kwil
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 7z8ksks6mFBO for <kitten@ietfa.amsl.com>; Thu, 25 Mar 2021 05:11:08 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C9D73A1F77 for <kitten@ietf.org>; Thu, 25 Mar 2021 05:11:08 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 0F7A95C00E6 for <kitten@ietf.org>; Thu, 25 Mar 2021 08:11:05 -0400 (EDT)
Received: from imap34 ([10.202.2.84]) by compute4.internal (MEProxy); Thu, 25 Mar 2021 08:11:05 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samwhited.com; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=4AowfIRWNpLSm8SqggRgR/Md+9LSmv3 jqtNH8rbsGjs=; b=eBcSAAosz92xexnrKVmz7UEQyg8sqsHDkXL07tCrMxaw6e4 HR+Dyu3+JfbIkS7fAS4iWqEG2WWq9PK0LX+i+O85+DkttPa5ZkFn/ClbFzCHQ7Zh ejZeBLyHrgZa7/A2WZhI/PCcpf9F1NVHs8tBni02VqFiHdeNmAvwxJ59zA7WtSLM WMasU2fd03tQoODukK92+r/OBiIsl9avaYHYoV1YqoIhwNd2vNTdoK1cBO9pJmZ8 BPSBF3jXbOFY/6nTEh49HlWC1VzZFJc69pcir3NAxIS3jBLgUbLulI1c5sOdGv0F klnH24E4edniiDcFXYWV2QFDtj88YxQ27ONi1NA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=4AowfI RWNpLSm8SqggRgR/Md+9LSmv3jqtNH8rbsGjs=; b=TZb7kwilTknQqAhxA6TZOB JdiJ/M601Dp9/gERERv+SlXdh8kLF6QvEPiBBMKsiKab557gp+rlDbrF/h2EWJsM rjYU/sirikesEnr7amwMR+nlxBNCvNG8LLBrM9HTK5rHvceVT9LwWNlUIruraOIu cT3l3roUsgoIWhtklDcHiWAufY0kJUxpYFFDebJstcZi/rGB/pa5rcnqY9Dp4Vrx DCVl0qMvkav1CxeHtBf8p2JBUwdRb//s8xKm/tKzLMq6+Y55G51vsBZsuAzp8Isg Em6Njpx9QnznmZmJmeBMPr+iNURkwIeAj9930ofWCA+S++YS6xPWYUCWAWltXvAQ ==
X-ME-Sender: <xms:2H1cYO0DRx5esDGDsugGr2IArrYPfqiAyPdyIAdw4Jr85eUwtIQ_iw> <xme:2H1cYBG2NR4fUN4MD_dVDv_YIBEJ72E5BfFTsRxpF3m9UMKrwU-GQ0mQ_MSLLbXoJ npqQtOxDjcPnsT7Dg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudehtddgfeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreerjeenucfhrhhomhepfdfurghm ucghhhhithgvugdfuceoshgrmhesshgrmhifhhhithgvugdrtghomheqnecuggftrfgrth htvghrnheptdffhfeghfeujeejfeegheetjeevtdevleeiueffueevfefhudeutdetieff gfefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepsh grmhesshgrmhifhhhithgvugdrtghomh
X-ME-Proxy: <xmx:2H1cYG4jfqtHg-2ZLchZSByYyPf0DpV3fKEKOYyzBUpejG2a_LFzDw> <xmx:2H1cYP1V1areP9AUcZjghjZEreM_lTvnELk3qZohqikbKdIZ-xLXLQ> <xmx:2H1cYBGvlk9PZYAfdWlVBhhZr8AGyAWQF7pH1GVXLY0Rxu49eYARJg> <xmx:2X1cYFQfKVO-qUvJCg9HnjnADA2aIjkDAEcR9ZADM-g9g6FLtU86Og>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id A7611280074; Thu, 25 Mar 2021 08:11:04 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-273-g8500d2492d-fm-20210323.002-g8500d249
Mime-Version: 1.0
Message-Id: <313a79cb-b58e-4098-b79e-2030c4e77c15@www.fastmail.com>
In-Reply-To: <874kgztvs4.fsf@latte.josefsson.org>
References: <874kgztvs4.fsf@latte.josefsson.org>
Date: Thu, 25 Mar 2021 08:10:34 -0400
From: Sam Whited <sam@samwhited.com>
To: KITTEN Working Group <kitten@ietf.org>
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/NjuaROcwtd7LkMyi8qOqZjvbw1M>
Subject: Re: [kitten] SCRAM and draft-ietf-kitten-tls-channel-bindings-for-tls13
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, 25 Mar 2021 12:11:13 -0000

I don't really know what "Updates" means in this context, so I just put
an RFC that uses tls-unique. The point wasn't so much that it changes
any normative text, but that this document should be discoverable from
5802 so that if you read "tls-unique" then go up to the top and see
"Updated by <new TLS 1.3 unique CB RFC>" you have a chance at finding
and implementing this instead.

On Thu, Mar 25, 2021, at 05:41, Simon Josefsson wrote:
> Thanks for draft-ietf-kitten-tls-channel-bindings-for-tls13!  It is
> not clear to me that it would actually modify anything for SCRAM/GS2,
> would it?  Those documents still reference 'tls-uniqe' and things will
> still be broken, as far as I can tell.  Should the new draft update
> the SCRAM/GS2 specs?  I believe the channel binding flexibility in
> SCRAM/GS2 has been one complexity that has prevented adoption, but
> solving that may be too late but we may be able to solve the security
> issues.  I see that there is an 'Updates: 5802' but I can't find any
> text describing what is intendted to be changed.

v2.23.0 | Report a Bug | By Email