Re: [TLS] Better TLS Client Authentication
Phillip Hallam-Baker <phill@hallambaker.com> Thu, 26 May 2022 00:29 UTC
Return-Path: <hallam@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AF1FC2B71F6 for <tls@ietfa.amsl.com>; Wed, 25 May 2022 17:29:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level:
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0vXgwrxOxG-X for <tls@ietfa.amsl.com>; Wed, 25 May 2022 17:29:50 -0700 (PDT)
Received: from mail-yb1-f176.google.com (mail-yb1-f176.google.com [209.85.219.176]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8281C2AFFF7 for <tls@ietf.org>; Wed, 25 May 2022 17:29:50 -0700 (PDT)
Received: by mail-yb1-f176.google.com with SMTP id p190so470207ybg.4 for <tls@ietf.org>; Wed, 25 May 2022 17:29:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dJxygPsFtEd0UnuI3eJ441znktuAwS6SYwOdG4+6Jd8=; b=s+gd2+DoXSAUbZ7GxDae/R31Z2kz4/3TLpQVxENnlJUuSUpLDo+lnB60AAlAI7RMkC 8fQl1PcyjeeSJFhjR9/7iDQ6unoN+9rRWaqEbxXkYCLU0Rc9QBaeJgVB9PNYX6/84aID yHcfYNqUmH+5ySEGdjfHLGgIcQLTFNox1Ivar3AkFKkFoZJHMVFj1CifUYVsRJ5XeZIM SNJd7a8P+uj6GBpCQXBsVZx9PQWKf6BFGPNpPlZ+BSw2nU7jzK4oSRaH8mlDc7rTz41V MbhmjyuIZThHJQ/2IRLgqUZELtJc98F0MCxm7C6F3GZ1Z7pn2wVokw1dWpSc/6kFSCz7 OLXQ==
X-Gm-Message-State: AOAM533oyzFutVKGjTfQ+gfgviAefELqXvDJvRi6zOAdv+eSwGWoVqaG 7v7yhvc08zWJEy/MMRLDLwDc0Jq4HjgqH3JnXJk=
X-Google-Smtp-Source: ABdhPJy8mKLx/zjmOuikbVWQMY41c7+N3BWG+NCwvmelU/R4QkqW/QYGPx0LnXyhwwdm2rp3L8Wo9yAuj8Sh0fMiFPo=
X-Received: by 2002:a25:3b13:0:b0:64e:3a3f:f7fb with SMTP id i19-20020a253b13000000b0064e3a3ff7fbmr32885716yba.463.1653524990076; Wed, 25 May 2022 17:29:50 -0700 (PDT)
MIME-Version: 1.0
References: <CAMm+LwiWnpZ7R3X_FvZijwK=WEcSnTZNEEkX19GdKvkmXwt0NA@mail.gmail.com> <515c6c4f-4b3a-3145-9e45-e62908e1eaf4@gmail.com>
In-Reply-To: <515c6c4f-4b3a-3145-9e45-e62908e1eaf4@gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 25 May 2022 20:29:39 -0400
Message-ID: <CAMm+Lwi2pFuhrxpco171A7kP+ijHZ5e02DZeuWimTcAc_7onuQ@mail.gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
Cc: tls@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a9313105dfdf4903"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/wWNA4fF-cYI9lsrnoczqRg2GDWY>
Subject: Re: [TLS] Better TLS Client Authentication
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 May 2022 00:29:52 -0000
On Tue, May 24, 2022 at 12:59 AM Anders Rundgren < anders.rundgren.net@gmail.com> wrote: > Hi Phillip, > I'm not able to figure out the merits of your proposal, but I see one > major obstacle: Google have a de-facto monopoly (80%) on browser technology > and your proposal seems to require a rather substantial upgrade. > NO! No browser update needed! No server update needed! The only thing missing is the private key management for the user. And that can all be done by a standalone app.
- [TLS] Better TLS Client Authentication Phillip Hallam-Baker
- Re: [TLS] Better TLS Client Authentication Anders Rundgren
- Re: [TLS] Better TLS Client Authentication Tim Cappalli
- Re: [TLS] Better TLS Client Authentication Blumenthal, Uri - 0553 - MITLL
- Re: [TLS] Better TLS Client Authentication Jonathan Hoyland
- Re: [TLS] Better TLS Client Authentication Phillip Hallam-Baker
- Re: [TLS] Better TLS Client Authentication Phillip Hallam-Baker
- Re: [TLS] Better TLS Client Authentication Blumenthal, Uri - 0553 - MITLL
- Re: [TLS] Better TLS Client Authentication Phillip Hallam-Baker