[quicwg/base-drafts] Why must we not use post-handshake client auth? (#2294)
David Schinazi <notifications@github.com> Fri, 04 January 2019 19:54 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 4354B130E89 for <quic-issues@ietfa.amsl.com>; Fri, 4 Jan 2019 11:54:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.519
X-Spam-Level:
X-Spam-Status: No, score=-6.519 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 QpUUxx6kedxz for <quic-issues@ietfa.amsl.com>; Fri, 4 Jan 2019 11:54:11 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 755A7130E85 for <quic-issues@ietf.org>; Fri, 4 Jan 2019 11:54:11 -0800 (PST)
Date: Fri, 04 Jan 2019 11:54:10 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1546631650; bh=E7/YVQqEZv5wvIXQRfVlVULRKae7zEa8H8D11stvQDo=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=fO1ajWdiXdJmSYdt1IHJrc21a53UQXRbZV9V3TFwpBASAhzVINahqvWnwXpRCyoZl g7P3bGMt3X1NuquVux1xVZ2MpmvqLPj6KqQiRjTxSIL9Z7/9GQrcZ6eSc6B04VrGBq E3WEz3IUlxdZHFxLvUgUe0mQwVN3aOuhIk/X9er4=
From: David Schinazi <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab36550505fd2f1d25fe5a9fb8c6c059cf7beee6a092cf0000000118477be292a169ce179b352f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2294@github.com>
Subject: [quicwg/base-drafts] Why must we not use post-handshake client auth? (#2294)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c2fb9e243723_5fa93fb7406d45c018793c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DavidSchinazi
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/9BIOg7IFflac-fZ5nvyxbZnI1zs>
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: Fri, 04 Jan 2019 19:54:13 -0000
draft-tls section 4.4 (Peer Authentication) states: > A server MUST NOT use post-handshake client authentication (see Section 4.6.2 of [TLS13]). Why is that? Could we add a sentence explaining why not, or a reference? -- 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/issues/2294
- [quicwg/base-drafts] Why must we not use post-han… David Schinazi
- Re: [quicwg/base-drafts] Why must we not use post… Martin Thomson
- Re: [quicwg/base-drafts] Why must we not use post… Martin Thomson
- Re: [quicwg/base-drafts] Why must we not use post… Martin Thomson
- Re: [quicwg/base-drafts] Why must we not use post… David Schinazi