Re: [OAUTH-WG] Call for Adoption - OAuth Proof of Possession Tokens with HTTP Message Signature

Aaron Parecki <aaron@parecki.com> Fri, 08 October 2021 04:14 UTC

Return-Path: <aaron@parecki.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86AA13A09DD for <oauth@ietfa.amsl.com>; Thu, 7 Oct 2021 21:14:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=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=parecki.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 2F7DTiz8PrkP for <oauth@ietfa.amsl.com>; Thu, 7 Oct 2021 21:13:59 -0700 (PDT)
Received: from mail-io1-xd31.google.com (mail-io1-xd31.google.com [IPv6:2607:f8b0:4864:20::d31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DACFE3A09D6 for <oauth@ietf.org>; Thu, 7 Oct 2021 21:13:58 -0700 (PDT)
Received: by mail-io1-xd31.google.com with SMTP id m20so8428867iol.4 for <oauth@ietf.org>; Thu, 07 Oct 2021 21:13:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parecki.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=peDXT/xcVBYMUX0+57lJ7S470ENksCHw0/lTJg0Rq2Q=; b=kf+Isixi4s6YClTcEcXd+Ij96U3C1LwLbY1UUmzKCq9QA42nkUCK7nqzJJt0cg13F0 u9fumxy2iEeo9biZWx44QLK1iksrrOBVBEQKo8bCGj7p/3rYc4NfVWJXOWDsHmiaJX/l u3pVzTqWta4yUOu6vnlikSqjktVQr/x52807jbBXFlmEDLtrwdQoQby2tevQnwow4hMG prnf7PIlL7iGKKPQw49Qj+6k34SduAnpMKZpc4mCM4flfxNXyPuYtUHLlOMb1LGCeOCS 7WxcZOXl5UbG6qwtVMktI2I/VtekmsI11Tnq6yZZMLzHBJYWMrFhSnk+Bk789mOtKYu5 Ir3Q==
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=peDXT/xcVBYMUX0+57lJ7S470ENksCHw0/lTJg0Rq2Q=; b=F+2zUGyUMA5upYcV4xwkV2X+X5sIxXSMkYU9etxYsB5qftymHRgn+ONfD4WjuFsgXt ue7ExjaXbJkPAx5kIT/l/UWdrJlnrmDGYoYe5WR/p/Ejl8iAyWqd/1Ulkk7K8Fr52n1f ULqV3tsBj36DQym1O9Z/0wBqbwV/CPY5q4/MRSp3RY9eG3T6ZBu11oJT82ig9A3XWkGa bxoMEMyoKSyaVivyb++ZEeeBG4c/u11gtV2Doyn7Bcv+FOhf7Gpf3BbvaQox4WURAcNo mSrPYXftfOj/N2PkzmFCu3np1V+tQhVvDuoP9MCePlEjD9aZspjxjSC89Vvp6bivrw61 j3lw==
X-Gm-Message-State: AOAM533LaAvVt6tnLJBWJHm+xHI1wL6QmoE3ZUbku/820dBBykzHE/kL XJwhh2J7HXU6ZF9NP08pd4qK0hwtxFXe8w==
X-Google-Smtp-Source: ABdhPJwPyHRUK6sufBhuuCAK+K5JCEiwz9rjIoKQaigSFcB7rvzR32gsoKQ2Bf0a9vFaZBflcuS90Q==
X-Received: by 2002:a6b:7a0a:: with SMTP id h10mr5897981iom.20.1633666437232; Thu, 07 Oct 2021 21:13:57 -0700 (PDT)
Received: from mail-io1-f43.google.com (mail-io1-f43.google.com. [209.85.166.43]) by smtp.gmail.com with ESMTPSA id a8sm457135iok.36.2021.10.07.21.13.56 for <oauth@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 07 Oct 2021 21:13:56 -0700 (PDT)
Received: by mail-io1-f43.google.com with SMTP id n7so349205iod.0 for <oauth@ietf.org>; Thu, 07 Oct 2021 21:13:56 -0700 (PDT)
X-Received: by 2002:a05:6638:2516:: with SMTP id v22mr6061089jat.17.1633666436128; Thu, 07 Oct 2021 21:13:56 -0700 (PDT)
MIME-Version: 1.0
References: <CADNypP9QXCEjJmkhBvTHn68kDcJ2Mfg-tSQx1-hvfPoOTXCKzA@mail.gmail.com> <59DBD0A1-7C36-47D1-9F4C-AFE5EA8458E1@forgerock.com> <CAFvbn=ZRCGoLtZ1DidZa0KYR0-zMTVSfCQEJ+7YyScYXUf84Fw@mail.gmail.com>
In-Reply-To: <CAFvbn=ZRCGoLtZ1DidZa0KYR0-zMTVSfCQEJ+7YyScYXUf84Fw@mail.gmail.com>
From: Aaron Parecki <aaron@parecki.com>
Date: Thu, 07 Oct 2021 21:13:45 -0700
X-Gmail-Original-Message-ID: <CAGBSGjqA+1S_S25HmcmsdohwAtBfcLKcX3fNpxNv1Dgq5j0Yow@mail.gmail.com>
Message-ID: <CAGBSGjqA+1S_S25HmcmsdohwAtBfcLKcX3fNpxNv1Dgq5j0Yow@mail.gmail.com>
To: Ash Narayanan <ashvinnarayanan@gmail.com>
Cc: Neil Madden <neil.madden@forgerock.com>, Warren Parad <wparad@rhosys.ch>, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009b66e905cdcf9b22"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/1M94hauftuYY_trQbCw69qpPJs8>
Subject: Re: [OAUTH-WG] Call for Adoption - OAuth Proof of Possession Tokens with HTTP Message Signature
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Oct 2021 04:14:04 -0000

> obviously we can't use any sensitive keys with these

That's not true at all, public clients can use keys that they create
themselves or are issued to a particular instance. That's one of the
reasons we are giving a name to this type of client in OAuth 2.1, a
"credentialed" client.

A public client clearly can't share credentials with other instances of the
public client, but there's no reason they can't use a key that is only ever
known to them.




On Thu, Oct 7, 2021 at 9:06 PM Ash Narayanan <ashvinnarayanan@gmail.com>
wrote:

> Oh geez, yesterday was my day off but ended up down a deep rabbit hole
> after reading this draft and the ones that came before it.
>
> I do not support adoption and was going to list my reasons but Warren
> Parad beat me to it.
>
> In addition to the list he has provided, I'd also like to see the draft
> make a mention of public clients; obviously we can't use any sensitive keys
> with these.
>
>
> Regards,
> Ash
>
> On Thu, Oct 7, 2021 at 11:02 PM Neil Madden <neil.madden@forgerock.com>
> wrote:
>
>> Canonicalised signature schemes inevitably lead to cryptographic doom,
>> and should die with SAML (ha!). For that reason I do not support adoption
>> of this draft.
>>
>> I also think the arguments for canonicalisation vanish as soon as you
>> want end-to-end confidentiality too.
>>
>> — Neil
>>
>> On 6 Oct 2021, at 22:02, Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com>
>> wrote:
>>
>> 
>> All,
>>
>> As a followup on the interim meeting today, this is a *call for adoption
>> *for the *OAuth Proof of Possession Tokens with HTTP Message Signature* draft
>> as a WG document:
>> https://datatracker.ietf.org/doc/draft-richer-oauth-httpsig/
>>
>> Please, provide your feedback on the mailing list by* October 20th*.
>>
>> Regards,
>>  Rifaat & Hannes
>>
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>>
>>
>> Manage My Preferences <https://preferences.forgerock.com/>, Unsubscribe
>> <https://preferences.forgerock.com/>
>>
>> _______________________________________________
>> OAuth mailing list
>> OAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/oauth
>>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
-- 
---
Aaron Parecki
https://aaronparecki.com