Re: [jose] JWK Thumbprint in JWS/JWE Header

Nathaniel McCallum <npmccallum@redhat.com> Tue, 19 July 2016 16:14 UTC

Return-Path: <npmccallum@redhat.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7883012D6B3 for <jose@ietfa.amsl.com>; Tue, 19 Jul 2016 09:14:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.209
X-Spam-Level:
X-Spam-Status: No, score=-7.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 RY1twRT3goeN for <jose@ietfa.amsl.com>; Tue, 19 Jul 2016 09:14:06 -0700 (PDT)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 432D612D79B for <jose@ietf.org>; Tue, 19 Jul 2016 09:09:26 -0700 (PDT)
Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id DBD36C0467C8; Tue, 19 Jul 2016 16:09:25 +0000 (UTC)
Received: from unused (unused [10.10.51.88] (may be forged)) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u6JG9Oep026887 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 19 Jul 2016 12:09:25 -0400
Message-ID: <1468944564.8067.95.camel@redhat.com>
From: Nathaniel McCallum <npmccallum@redhat.com>
To: Justin Richer <jricher@mit.edu>
Date: Tue, 19 Jul 2016 12:09:24 -0400
In-Reply-To: <F817D984-D424-4335-BBC4-3CC88B1C8223@mit.edu>
References: <1468939736.8067.91.camel@redhat.com> <F817D984-D424-4335-BBC4-3CC88B1C8223@mit.edu>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Tue, 19 Jul 2016 16:09:25 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/5AOaADQwj60ceBTaLMDITJewOmw>
Cc: jose@ietf.org
Subject: Re: [jose] JWK Thumbprint in JWS/JWE Header
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose>, <mailto:jose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jose/>
List-Post: <mailto:jose@ietf.org>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose>, <mailto:jose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jul 2016 16:14:09 -0000

Has there been any talk about using a prefix to specify the hash algo?

On Tue, 2016-07-19 at 11:24 -0400, Justin Richer wrote:
> This was discussed on the list a while ago, and the thought was that
> you could easily use the JWK thumbprint *as* the “kid” value instead
> of defining a new field for this use case. The header values are
> protected by the signature in the normal (compact) JWS/JWE formats,
> and ought to be protected in the JSON representations too for exactly
> the reasons you’re talking about. 
> 
>  — Justin
> 
> > 
> > On Jul 19, 2016, at 10:48 AM, Nathaniel McCallum <npmccallum@redhat
> > .com> wrote:
> > 
> > The JWS and JWE specs defined the "kid" header value that can be
> > used
> > to identify the key used for signing or encryption. Subsequently,
> > the
> > JWK thumbprint method was defined.
> > 
> > Has anyone put any thought into registering a header value for JWS
> > and
> > JWE headers that indicates the thumbprint of the key used for
> > signing
> > or encryption? This would be very helpful for key indexes
> > especially
> > when using unprotected headers since the value of "kid" might be
> > modified.
> > 
> > _______________________________________________
> > jose mailing list
> > jose@ietf.org
> > https://www.ietf.org/mailman/listinfo/jose
>