Re: [jose] JOSE Hash-algorithm Identifiers?

Anders Rundgren <anders.rundgren.net@gmail.com> Fri, 04 March 2016 18:46 UTC

Return-Path: <anders.rundgren.net@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C6551A8776 for <jose@ietfa.amsl.com>; Fri, 4 Mar 2016 10:46:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 Iew9CdAUA_Zd for <jose@ietfa.amsl.com>; Fri, 4 Mar 2016 10:46:42 -0800 (PST)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 C3D321A8774 for <jose@ietf.org>; Fri, 4 Mar 2016 10:46:41 -0800 (PST)
Received: by mail-wm0-x232.google.com with SMTP id p65so2927950wmp.0 for <jose@ietf.org>; Fri, 04 Mar 2016 10:46:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=IHDosiW02U4zp7IVtJOFOyC0ohLfbMsvJk4vT281Ztg=; b=dwe876gkL1zEi+NPE+li+gTSjReq8HginIghpvTSjrQyuwwf3BTTjHXcj1p2ICBFd/ QnlZV9yq4ZFX6Dby/IHgGEe4KsKvZaW5ooQ9V9XTspWACMyaMfBYKD5UTy0n8FZ0pJA4 6D2fKhlMOBDOFgZLJLbIP3bozuSBHNhKkKkqzUcwVuWuBUsgWFYUK9Cxp+FwwilLFxtJ 5+X3UN2GaMI/+73I7x66Di8gc1Uz0o1miLJJuvD327Z5d/0vmaqvKoBeQ4DQzGAgYYQo ATNqLKyU0s+nbDlnFV8R4ST3MzjdmMxT92BAOllwrPt5nE7/duy37dhIAEfCGKStwDmx leIA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=IHDosiW02U4zp7IVtJOFOyC0ohLfbMsvJk4vT281Ztg=; b=GzkB39yRMLFJjyurP6oVpw22bXAVvaqVgFNXF3Zk7qljIRbW50AAUBuoectAOohkyj 5vtf4VlogwzFFTjPmmogb9x2WZ0+Y/bHk2bPz8gDzoYke2Y8g4B1ZB0bhNssPGDvJlrL GrQ9kiAh1W2IxsVM5DAg6XjRnxoIAlR7kWg7gpNAwmCcDx2dhdDxAG3klOHER2nPaZkH EgwNmrIBy/sk4GCw/RBOVhhF3OSBTexYtvAvMvaypyhDfHfnT8FQsxd//DsU986nxJER /EvDPdZxsbsDYaFtqKbjpFSlaHdEPUxe5zW1/wnDGOzmLIBKi0sci0+wUAIP5Kkf2vPz jTYA==
X-Gm-Message-State: AD7BkJJHLevN/eZZZuADMHsPB1c2fOF169ikf2dZbt+0t94eKW0AYZN3xJTiC0+xVC5kfw==
X-Received: by 10.28.109.150 with SMTP id b22mr397777wmi.27.1457117200315; Fri, 04 Mar 2016 10:46:40 -0800 (PST)
Received: from [192.168.1.79] (83.203.130.77.rev.sfr.net. [77.130.203.83]) by smtp.googlemail.com with ESMTPSA id p191sm4726257wmb.0.2016.03.04.10.46.38 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Mar 2016 10:46:38 -0800 (PST)
To: Mike Jones <Michael.Jones@microsoft.com>, "jose@ietf.org" <jose@ietf.org>
References: <5667D450.7090503@gmail.com> <56D9A975.2050107@gmail.com> <SN1PR0301MB164584E7697015DC87FC2197F5BE0@SN1PR0301MB1645.namprd03.prod.outlook.com>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <56D9D7F1.9070107@gmail.com>
Date: Fri, 04 Mar 2016 19:46:09 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <SN1PR0301MB164584E7697015DC87FC2197F5BE0@SN1PR0301MB1645.namprd03.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/jose/bIyZnkOv9e12wvuCRY2NvqU0uuY>
Subject: Re: [jose] JOSE Hash-algorithm Identifiers?
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 04 Mar 2016 18:46:43 -0000

On 2016-03-04 18:36, Mike Jones wrote:
> The PKCE RFC [RFC 7636] also uses "S256".

Since this points to a rather specific application, I'm not sure if this speaks for or against using S256 for indicating SHA256...

Anders

>
> -----Original Message-----
> From: jose [mailto:jose-bounces@ietf.org] On Behalf Of Anders Rundgren
> Sent: Friday, March 4, 2016 7:28 AM
> To: jose@ietf.org
> Subject: Re: [jose] JOSE Hash-algorithm Identifiers?
>
> No takers on this one?
>
> On 2015-12-09 08:12, Anders Rundgren wrote:
>> The following extract from a recent ACME posting indicates that I'm not the only one who see use-cases for such:
>>
>> It's not a bad idea to specify the agreement-integrity as a dictionary
>> instead so in that future case, there's not problem of checksum
>> negotiation:
>> "agreement-integrity": {"sha512":
>> "3Ys8QL9di54ggXIGBAS2RHr_W6cMurZPizhZihkQjwl3VG2dpXZYmsYZ0B7LG-tWlVE9-
>> Hwp9hL3Mosvbr6lCA"}
>>
>> In my work I used the names S128, S256, and S512.
>>
>> Anders
>>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>