IETF Logo Mail Archive

Re: [jose] "x5c" - JSON Compatible?

Mark Watson <watsonm@netflix.com> Tue, 13 January 2015 16:52 UTC

Return-Path: <watsonm@netflix.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 A55DA1A8F4A for <jose@ietfa.amsl.com>; Tue, 13 Jan 2015 08:52:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 PQagifb68HU1 for <jose@ietfa.amsl.com>; Tue, 13 Jan 2015 08:52:48 -0800 (PST)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0DBB1A8F44 for <jose@ietf.org>; Tue, 13 Jan 2015 08:52:47 -0800 (PST)
Received: by mail-wi0-f177.google.com with SMTP id l15so5290366wiw.4 for <jose@ietf.org>; Tue, 13 Jan 2015 08:52:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netflix.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6AGzb/fyOec92DQMdeCZoZtPIbHlA2Bszo1gwwUO8uo=; b=UhdDkr0CUijc1LswZhuLk1npfKmcZDA5jRRI3BJUMOUpPBsVkbslt8UFeB2LhruVaM qVrpsltEwqAB3RHVHNcoz2Y/OxR93IJN5haMW9BLK2v9yCTNeSbED/TDNk3IulwrRF0I zbI6zEIvgTJVzsd0YPeV/rTr1Q9rDGSknw55A=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=6AGzb/fyOec92DQMdeCZoZtPIbHlA2Bszo1gwwUO8uo=; b=Bx+vqiLrADlmbaUkYEMZtztHxWQNkRlUBzzwv2eZ4S5JOUxiKxgs8H+azL6JgcuAsU zbXhMPBnevdkWxn/Sjnxyos11s9yWPaLINoj/M18NCFerCZ5tgGrgz3QTxqgDjUW7mfn bRObXFmrXyosqYw8z/JyO2hd1RSQYtQDgQ6DovfmJ3xi+dhtZORxgveITvq9+ZXoXg3h oSfRq2G1skXHXFm1ctLph0Wpkuf6iFJChj4fj/3yStFIRJCb+PPoaY8ruKCTHhRkqhW/ TMUQ2zdKR+7/vFg6CHPuv2QVQx3LiU4UnQroEqUWazCY5+PTKkJJhP4zdeRW2hragAxj D+vg==
X-Gm-Message-State: ALoCoQkWpnTKg+oLHXkvCEWfG6Ts0AIuA89TNPOVucGVoN/P2jist1RXdbf8rRmo8C/j4TeA+KgI
MIME-Version: 1.0
X-Received: by 10.180.76.239 with SMTP id n15mr42474479wiw.66.1421167966175; Tue, 13 Jan 2015 08:52:46 -0800 (PST)
Received: by 10.27.94.5 with HTTP; Tue, 13 Jan 2015 08:52:46 -0800 (PST)
In-Reply-To: <54B50BF4.5080709@gmail.com>
References: <54B4ED80.2060501@gmail.com> <CAL02cgRQEnM+d4CnwxR=HL1QOQbS6fQyU894spv2Wj-zFhi4Hg@mail.gmail.com> <54B50BF4.5080709@gmail.com>
Date: Tue, 13 Jan 2015 08:52:46 -0800
Message-ID: <CAEnTvdA853xqpzJb0_Skjbg1RT3zngAwzU6iEiB0OQzDP5hUVQ@mail.gmail.com>
From: Mark Watson <watsonm@netflix.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
Content-Type: multipart/alternative; boundary="f46d043749b3ca5d7e050c8b7340"
Archived-At: <http://mailarchive.ietf.org/arch/msg/jose/id21Tj5H_CQvM49T18RU4KpmvHU>
Cc: Richard Barnes <rlb@ipv.sx>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] "x5c" - JSON Compatible?
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: <http://www.ietf.org/mail-archive/web/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, 13 Jan 2015 16:52:49 -0000

On Tue, Jan 13, 2015 at 4:13 AM, Anders Rundgren <
anders.rundgren.net@gmail.com> wrote:

> On 2015-01-13 12:35, Richard Barnes wrote:
>
>>
>>
>> On Tuesday, January 13, 2015, Anders Rundgren <
>> anders.rundgren.net@gmail.com <mailto:anders.rundgren.net@gmail.com>>
>> wrote:
>>
>>     The spec claims the following:
>>
>>        "Note that since these strings contain base64 encoded
>>        (not base64url encoded) values, they are allowed to contain
>>        white space and line breaks."
>>
>>     Is this really JSON compliant?
>>
>>     I didn't interpret the JSON spec in that way and Python and Chrome
>> seems to agree with me.
>>
>>     What's I'm missing here?
>>
>>
>> Are you seriously suggesting that JSON strings can't contain white space?
>>
>> Control characters have to be escaped, but they can definitely be there.
>>
>> JSON.parse('["this is...\\u000A...a string"]')
>>
>
> Sure, but the example in appendix B wouldn't parse.
> Shouldn't a proper text say that possible line-breaks MUST be properly
> escaped.
>

​Line breaks in JSON do have to be escaped, either as above or with \r \n.
This is clear at www.json.org.

…Mark​



>
> Anders
>
>
>> --Richard
>>
>>
>>     Cheers
>>     Anders
>>
>>     _________________________________________________
>>     jose mailing list
>>     jose@ietf.org
>>     https://www.ietf.org/mailman/__listinfo/jose <
>> https://www.ietf.org/mailman/listinfo/jose>
>>
>>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>

v2.23.0 | Report a Bug | By Email