Re: [quicwg/base-drafts] Clarify why post-handshake client auth is banned (#3044)
David Benjamin <notifications@github.com> Tue, 17 September 2019 18:14 UTC
Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 500B81209E0
for <quic-issues@ietfa.amsl.com>; Tue, 17 Sep 2019 11:14:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Level:
X-Spam-Status: No, score=-6.596 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1,
DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404,
HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5,
SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
header.d=github.com
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 4IxpvWxKuIoK for <quic-issues@ietfa.amsl.com>;
Tue, 17 Sep 2019 11:14:13 -0700 (PDT)
Received: from out-20.smtp.github.com (out-20.smtp.github.com [192.30.252.203])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 4C5061209A3
for <quic-issues@ietf.org>; Tue, 17 Sep 2019 11:14:13 -0700 (PDT)
Date: Tue, 17 Sep 2019 11:14:12 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2014; t=1568744052;
bh=KOELfTAxOk7ndpvjMKFc3toigJO0guBBCYNs+VXiwtQ=;
h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=BBv3UPtB8kU80NnKa8Fo8mFZCWrV0rhosPtmIICYdlXyQLx/sKyRcxsFApSR8/UYl
iGTsB+PIzk8acIbQIe31Gl00STwUjUzTddlU+mlk+79ATiAAUgY/oR2Ps6nwy6cp1Y
JYXoGxOAxEbdkFHUmr+HxZ5MZ+fc6I7nqi2eOERw=
From: David Benjamin <notifications@github.com>
Reply-To: quicwg/base-drafts
<reply+AFTOJK6R5X7BVWT2MR32NEF3RZRQJEVBNHHB26CFR4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3044/review/289453567@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3044@github.com>
References: <quicwg/base-drafts/pull/3044@github.com>
Subject: Re: [quicwg/base-drafts] Clarify why post-handshake client auth is
banned (#3044)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_5d8122745d164_33433f8163ccd96c4110c7";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: davidben
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/wfidj3wM7Zag_PeVaUaotGAH7xo>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG
<quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>,
<mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>,
<mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2019 18:14:21 -0000
davidben commented on this pull request.
> @@ -612,8 +612,13 @@ MAY refuse a connection if the client is unable to authenticate when requested.
The requirements for client authentication vary based on application protocol
and deployment.
-A server MUST NOT use post-handshake client authentication (see Section 4.6.2 of
-{{!TLS13}}).
+A server MUST NOT use post-handshake client authentication (as defined in
+Section 4.6.2 of {{!TLS13}}), because the multiplexing offered by QUIC prevents
+clients from correlating the certificate request with the application-level
+event which triggered it (see {{?HTTP2-TLS13=I-D.ietf-httpbis-http2-tls13}}).
Likewise. :-)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/3044#discussion_r325314195
- [quicwg/base-drafts] Clarify why post-handshake c… David Schinazi
- Re: [quicwg/base-drafts] Clarify why post-handsha… Marten Seemann
- Re: [quicwg/base-drafts] Clarify why post-handsha… Martin Thomson
- Re: [quicwg/base-drafts] Clarify why post-handsha… David Schinazi
- Re: [quicwg/base-drafts] Clarify why post-handsha… David Schinazi
- Re: [quicwg/base-drafts] Clarify why post-handsha… David Benjamin
- Re: [quicwg/base-drafts] Clarify why post-handsha… Martin Thomson