Re: [jose] Canonical JSON form

Tim Bray <tbray@textuality.com> Mon, 29 October 2018 13:38 UTC

Return-Path: <tbray@textuality.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 7CE83130F23 for <jose@ietfa.amsl.com>; Mon, 29 Oct 2018 06:38:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=textuality-com.20150623.gappssmtp.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 XtgdbUwAki5K for <jose@ietfa.amsl.com>; Mon, 29 Oct 2018 06:38:55 -0700 (PDT)
Received: from mail-ed1-x544.google.com (mail-ed1-x544.google.com [IPv6:2a00:1450:4864:20::544]) (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 85FF1130DBE for <jose@ietf.org>; Mon, 29 Oct 2018 06:38:54 -0700 (PDT)
Received: by mail-ed1-x544.google.com with SMTP id u12-v6so4435962eds.4 for <jose@ietf.org>; Mon, 29 Oct 2018 06:38:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/cubA8EJjbKTSBCExKYKFgnbh3vM/mZ8DUtQ8U+9MWA=; b=qFRBtgMSOx2GbrgRuMg2DmKnVQ+NTJfdDvm1Pq55P6xu/Erkrr0IDg0Bd+k54e+9mx VEeGfYUtI7zi2+i5kGI8Jq8Ea4fkuQB8a2Q5vYWX7j7SLEnY2DLGn3zp2wMEbNcaR1sf m+g6aBemLtqu8gGd2BDHQNjl2vNWd05i3XQ6GTg8kVsNMjFxr+JVpqC3FFs8qn3nFG3r ZtDSvqCeEUC0V7LwbRH7iciiZpHoQcvbuNdVUeqbL0+suO9TWPLUbKTC/Ldje07vZRE8 0/n9QX1+3lsc3zj0jAPXO4Q/6QYV6airVZ7IpKOJyTsjEAuaRoowSmqwBP3GZrI3Q6T5 yeqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/cubA8EJjbKTSBCExKYKFgnbh3vM/mZ8DUtQ8U+9MWA=; b=RRJ0JzT4cmgHmjb5mZfFubx2AKZa2jzyR/90uBoxcAf1lwdQzz2DcU9bi2rZxnA+Vn oDDsV88YWqEt1k2OBPF5Yy6qUhCMQ2moJ++pKKH0c/L4SvPRaZT4pOTIvTbvVbSiq/8m /ijXwZfOT0FZCzWCidiIhakokEnwKzqmLBE41B4blfHcYIb1UBkuT2p8X9btnu5dTDWY XGl0uH9fL/FU8rIuxbkSd11AobxCba8j6VqALd9g9Wz+cko/AAewyhMDurb2z0OWy8ek LGhAbkcD+0woCWKuLST/BHop7+lU1X4NuXQeRGizA96QgMHRv07f8kdyq+FBsOf9PrFD +hyw==
X-Gm-Message-State: AGRZ1gJzifL92Kwt1LqvAzKHNIY7N/dMtSqaaU3GvokIJkgwJTAdmxxh A8CcKKiJUsChfx40KBowqsgDlJAiAcNF5ntnAth6nQ==
X-Google-Smtp-Source: AJdET5ekr14WzkI8apbeoJheUn/ppTWyMW6UyY7eHVJfeLkM0WVKIFBRJUrL4jevOvwFF8WI7YiEestzWAqgsleSlxc=
X-Received: by 2002:a17:906:1d5b:: with SMTP id o27-v6mr10567669ejh.61.1540820332887; Mon, 29 Oct 2018 06:38:52 -0700 (PDT)
MIME-Version: 1.0
References: <12DD2F97-80C3-4606-9C6B-03F7A4BF19DE@gmail.com> <8436AEE7-B25A-4538-B8F6-16D558D9A504@gmail.com> <MEAPR01MB35428606C09BF315DE04CC79E5E10@MEAPR01MB3542.ausprd01.prod.outlook.com> <CAHbuEH6DCD7Zc+PK3TnCBkKv1esnROwyCcDb8ZR+TKwgQQ+yXQ@mail.gmail.com> <0E6BD488-74D5-4640-BC31-5E45B0531AFC@gmail.com> <CAHbuEH5oH-Km6uAjrSr0pEHswFBLuDpfVweQ+gpj472yk+8iTQ@mail.gmail.com> <073CB50F-8D91-4EF6-90BE-FC897D557AA6@oracle.com> <A37D69B1-6B77-4E11-8BB9-A0209C77752C@tzi.org> <45bf6c0f-e510-4afc-4277-bdd486a8ce8c@gmail.com> <213796DB-D875-46B0-9F3C-1A56F9E154BA@gmail.com> <ff1dcd4e-2bf4-b85b-dde3-2cc8fe29fb17@gmail.com> <447AB837-7208-4A96-91CC-89D30A2734FA@gmail.com> <24cc6bb7-ea40-1a9c-8847-8d6c74131587@gmail.com> <92B9F9AF-BBCA-472D-9155-935F695CE7CE@gmail.com> <3b6a338b-5588-deb2-9a9c-23e0cc24a2f1@gmail.com> <FE6C1732-D16A-4D97-99F4-1350AF23A748@alkaline-solutions.com> <1B3A97D9-06BE-4225-BF8D-DE55C7FBF2DF@tzi.org> <CAF2hCbaPEdULLX41DeA_RMePZostcM46_eimQoR-NeE-JveHzg@mail.gmail.com> <2c5aa692-3458-b36f-23ae-c56d41deeff1@gmail.com>
In-Reply-To: <2c5aa692-3458-b36f-23ae-c56d41deeff1@gmail.com>
From: Tim Bray <tbray@textuality.com>
Date: Mon, 29 Oct 2018 06:38:40 -0700
Message-ID: <CAHBU6isO0Z0E9HihgGJuEykWpgpq0j=YReMFT=9U1Nd+F7dWog@mail.gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
Cc: Samuel Erdtman <samuel@erdtman.se>, Carsten Bormann <cabo@tzi.org>, jordan.ietf@gmail.com, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, jose@ietf.org, david@alkaline-solutions.com, James.H.Manger@team.telstra.com, Phil Hunt <phil.hunt@oracle.com>
Content-Type: multipart/alternative; boundary="0000000000009ad58f05795e300a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/JjgG6pWYVqsSwsD1hSf27T5cm1Y>
Subject: Re: [jose] Canonical JSON form
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Oct 2018 13:38:57 -0000

I like Samuel Erdtman's idea of starting with an open-source
implementation.  If I see one of those, with a convincing set of test
cases, I'd be inclined to make the case for spinning up a working group.

The argument isn't "Would it be useful?" it's "Can it be done?" So, start
by proving it can.

On Mon., Oct. 29, 2018, 1:33 a.m. Anders Rundgren <
anders.rundgren.net@gmail.com wrote:

> On 2018-10-28 21:32, Samuel Erdtman wrote:
> > In my opinion we can create a good canonicalization format for JSON to
> be used to sign cleartext JSON.
> >
> > As can be seen on this list many are skeptical so my approach would be
> to publish easy to use open source implementations.
>
> Yes, and part of that is supplying test data like:
> https://github.com/cyberphone/json-canonicalization/tree/master/testdata
> The Microsoft folks developing "Chakra" (their JS engine) already use the
> 100 million reference values.
>
>
> > If we do that and there is real interest then we might be able to
> convince people here about the need. In line with this ambition I have done
> the JS and Java publications. This might also show there is no actual
> interest and then that is also an outcome.
>
> Well, another part of the standards puzzle is getting early work into real
> products and services.
>
> FWIW, I'm personally involved in a couple of efforts using clear text JSON
> signatures:
> - Saturn, an open payment authorization scheme based on an enhanced "four
> corner" trust model which aims giving banks an upper hand against Apple
> Pay, Google Pay, PayPal, etc.
> - Mobile ID, an open, PKI-based, multi-issuer mobile authentication and
> signature solution for e-governments.
>
> Regards,
> Anders
>
> > Best regards
> > //Samuel
> >
> >
> > On Mon, Oct 22, 2018 at 8:44 AM Carsten Bormann <cabo@tzi.org <mailto:
> cabo@tzi.org>> wrote:
> >
> >     On Oct 22, 2018, at 04:47, David Waite <david@alkaline-solutions.com
> <mailto:david@alkaline-solutions.com>> wrote:
> >      >
> >      > intermittent interoperability failures until a new language
> runtime release which revises the numerical print and parse functions
> >
> >     Note that this is not a theoretical concern, as CVE-2010-4476 and
> CVE-2010-4645 amply demonstrate, nicely underscored by the re-occurrence of
> the latter in
> https://www.exploringbinary.com/php-converts-2-2250738585072012e-308-incorrectly/
> >
> >     Grüße, Carsten
> >
> >     _______________________________________________
> >     jose mailing list
> >     jose@ietf.org <mailto:jose@ietf.org>
> >     https://www.ietf.org/mailman/listinfo/jose
> >
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>