Re: Client Certificates - re-opening discussion
Eric Rescorla <ekr@rtfm.com> Sat, 19 September 2015 18:22 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4B051B630C for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 19 Sep 2015 11:22:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.289
X-Spam-Level:
X-Spam-Status: No, score=-6.289 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 9kCn6p-PD-RF for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 19 Sep 2015 11:22:25 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16B0C1B630B for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sat, 19 Sep 2015 11:22:24 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1ZdMin-00009s-L7 for ietf-http-wg-dist@listhub.w3.org; Sat, 19 Sep 2015 18:18:49 +0000
Resent-Date: Sat, 19 Sep 2015 18:18:49 +0000
Resent-Message-Id: <E1ZdMin-00009s-L7@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <ekr@rtfm.com>) id 1ZdMii-000097-Mc for ietf-http-wg@listhub.w3.org; Sat, 19 Sep 2015 18:18:44 +0000
Received: from mail-wi0-f177.google.com ([209.85.212.177]) by lisa.w3.org with esmtps (TLS1.2:RSA_ARCFOUR_SHA1:128) (Exim 4.80) (envelope-from <ekr@rtfm.com>) id 1ZdMih-0005Kn-7y for ietf-http-wg@w3.org; Sat, 19 Sep 2015 18:18:44 +0000
Received: by wicge5 with SMTP id ge5so68439573wic.0 for <ietf-http-wg@w3.org>; Sat, 19 Sep 2015 11:18:16 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=nXv/9/TxsAbrTsoiJOim0gwNTcI2uwQQVRdwYUD3Pqo=; b=F1snezPykclGRXX+n1dzQj+55Lia4ddGOCKqAgKPxWzSvm5STX03eSLHXxBvR0HxqL /W90YwoB3k53sAaNDbXfmpwed3wrJTvBq/StRH4yeUYtBAhlTrIeSjE5pu+h49NwDpHI cvQtsgvQBWpc8jzseSWVT4yrAAs7ClHbLsP1ImgPclGj7kGs/dILQ4HONP3zgXGNza8g U2EBdEddhnqjMmLdrX3KWrYFgqx81LBxdBCO17XE3aiY2vgYgpkzZCFPFzUtsSiqpQ3X ro2H2UlT7T2Oix2ikqmnrz9FlZkpGQfvsEwHV8HZsmzfERmN/mbM9zmsmj8djJXD+Hdz /rxw==
X-Gm-Message-State: ALoCoQmHtJxht+tfV8L/3V5+qFJK5k9/zU32Xpzqb/J7dE9fw2OHs/07plRRVglOkmIg5iKn5Kr7
X-Received: by 10.194.133.129 with SMTP id pc1mr13983308wjb.148.1442686695909; Sat, 19 Sep 2015 11:18:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.27.79.200 with HTTP; Sat, 19 Sep 2015 11:17:36 -0700 (PDT)
In-Reply-To: <70D2F8CE-D1A2-440F-ADFC-24D0CE0EDCF1@greenbytes.de>
References: <63DECDF0-AB59-4AFD-8E48-8C2526FD6047@mnot.net> <42DDF1C6-F516-4F71-BAE0-C801AD13AA01@co-operating.systems> <2F3BD1CB-042D-48AB-8046-BB8506B8E035@mnot.net> <CABcZeBNpjbNdeqxP_cwCDygk6_MVDoNhqcMEDmEvEBxztmonLg@mail.gmail.com> <20150918205734.GA23316@LK-Perkele-VII> <70D2F8CE-D1A2-440F-ADFC-24D0CE0EDCF1@greenbytes.de>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 19 Sep 2015 11:17:36 -0700
Message-ID: <CABcZeBPNxEA6O324tnF3dbUCLD-a7uUvWYYjO1pnYwAm9cN2eA@mail.gmail.com>
To: Stefan Eissing <stefan.eissing@greenbytes.de>
Cc: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>, Mark Nottingham <mnot@mnot.net>, Henry Story <henry.story@co-operating.systems>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="089e01227d9408432d05201dac41"
Received-SPF: none client-ip=209.85.212.177; envelope-from=ekr@rtfm.com; helo=mail-wi0-f177.google.com
X-W3C-Hub-Spam-Status: No, score=-8.3
X-W3C-Hub-Spam-Report: AWL=1.335, BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1ZdMih-0005Kn-7y d2a6942182c9269997124e6118660f64
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Client Certificates - re-opening discussion
Archived-At: <http://www.w3.org/mid/CABcZeBPNxEA6O324tnF3dbUCLD-a7uUvWYYjO1pnYwAm9cN2eA@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/30229
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
On Sat, Sep 19, 2015 at 12:18 AM, Stefan Eissing < stefan.eissing@greenbytes.de> wrote: > > > Am 18.09.2015 um 22:57 schrieb Ilari Liusvaara < > ilari.liusvaara@elisanet.fi>: > > > >> On Fri, Sep 18, 2015 at 01:48:50PM -0700, Eric Rescorla wrote: > >>> On Fri, Sep 18, 2015 at 10:05 AM, Mark Nottingham <mnot@mnot.net> > wrote: > >>> > >>> Hi Henry, > >>> > >>> Thanks, but this is a much more narrowly-scoped discussion -- how to > make > >>> client certs as they currently operate work in HTTP/2. > >> > >> > >> Is this a question about HTTP/2's limitations versus HTTP/1.1 or about > >> deficiencies > >> in HTTP/1.1 that HTTP/2 has not fixed? > > > > I think this is about the extra limitations of HTTP/2 regarding client > > authentication caused by major design differences between HTTP/1.1 and > > HTTP/2. > > > > Client certs in HTTP/1.1 aren't too great, but at least those don't > > seem to even remotely have the same problems as client certs in HTTP/2 > > (especially when in web environment). > > Just to have everyone on the same page. The problems - as we see them in > httpd - are > > 1. http/1.1 requests may trigger client certs which may require > renegotiation. Processing is no longer sequential with http/2, causing > conflicts. Well, presently renegotiation is illegal in HTTP/2, so this is a non-problem. However, I suppose if we land TLS 1.3 PR#209 it will come back. -Ekr > Even if mutexed what does connection state and h2 stream have to say to > each other and for how long? > > 2. connection reuse for different hosts is much more likely as a lot of > sites have a long list of subjectAltNames. That raises the likelihood of > conflicts as described above. > > Any advice on how to address this in an interoperable way is appreciated. > > //Stefan
- Client Certificates - re-opening discussion Mark Nottingham
- Re: Client Certificates - re-opening discussion Martin Thomson
- Re: Client Certificates - re-opening discussion henry.story@bblfish.net
- Re: Client Certificates - re-opening discussion Mark Nottingham
- Re: Client Certificates - re-opening discussion Ilari Liusvaara
- Re: Client Certificates - re-opening discussion henry.story@bblfish.net
- Re: Client Certificates - re-opening discussion Mike Belshe
- Re: Client Certificates - re-opening discussion Mark Nottingham
- RE: Client Certificates - re-opening discussion Mike Bishop
- Re: Client Certificates - re-opening discussion Ilari Liusvaara
- Re: Client Certificates - re-opening discussion Eric Rescorla
- Re: Client Certificates - re-opening discussion Ilari Liusvaara
- Re: Client Certificates - re-opening discussion Stefan Eissing
- Re: Client Certificates - re-opening discussion Eric Rescorla
- RE: Client Certificates - re-opening discussion Mike Bishop
- Re: Client Certificates - re-opening discussion Yoav Nir
- RE: Client Certificates - re-opening discussion Mike Bishop
- Re: Client Certificates - re-opening discussion Yoav Nir
- Re: Client Certificates - re-opening discussion henry.story@bblfish.net
- Re: Client Certificates - re-opening discussion Kyle Rose
- Re: Client Certificates - re-opening discussion Yoav Nir
- Re: Client Certificates - re-opening discussion Stefan Eissing
- Re: Client Certificates - re-opening discussion Kyle Rose
- Re: Client Certificates - re-opening discussion Mike Belshe
- Re: Client Certificates - re-opening discussion henry.story@bblfish.net
- Re: Client Certificates - re-opening discussion Stephen Farrell
- Re: Client Certificates - re-opening discussion Kyle Rose
- Re: Client Certificates - re-opening discussion Jason Greene
- Re: Client Certificates - re-opening discussion henry.story@bblfish.net
- RE: Client Certificates - re-opening discussion Mike Bishop
- Re: Client Certificates - re-opening discussion Stefan Eissing
- Re: Client Certificates - re-opening discussion henry.story@bblfish.net
- Re: Client Certificates - re-opening discussion Alex Rousskov
- Re: Client Certificates - re-opening discussion Mark Nottingham
- Re: Client Certificates - re-opening discussion Stefan Eissing
- Re: Client Certificates - re-opening discussion Martin Thomson
- RE: Client Certificates - re-opening discussion Mike Bishop
- Re: Client Certificates - re-opening discussion Yoav Nir
- Re: Client Certificates - re-opening discussion Ryan Hamilton