IETF Logo Mail Archive

Re: [jose] JWK member names, was: SECDIR review of draft-ietf-jose-json-web-key-31

Tim Bray <tbray@textuality.com> Mon, 15 September 2014 21:27 UTC

Return-Path: <tbray@textuality.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 7EA5E1A87AE for <jose@ietfa.amsl.com>; Mon, 15 Sep 2014 14:27:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 LVTVNYuyK5wZ for <jose@ietfa.amsl.com>; Mon, 15 Sep 2014 14:27:01 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D1891A87AF for <jose@ietf.org>; Mon, 15 Sep 2014 14:26:16 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id hy10so4123589vcb.3 for <jose@ietf.org>; Mon, 15 Sep 2014 14:26:15 -0700 (PDT)
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:from:date :message-id:subject:to:cc:content-type; bh=+oOlHJPo7Oe3B+5Ntx1KeS1LroL7umWS7sZXweVwRuw=; b=Qkp+RLZipgXLYeX/Nv/Mhrj1Zxl50W2zwj/29pnjdSUlv9zC0iLSzIMpNkfaDM+ZAF f2F674F5/SHvHtch5qaDW8tBvF8x0YHZOpS+CZR1KDayWgLQK56UGOddjsCssIbMs2QL LoCRqByQmAQZluVvQstmQs2viRq2pjoeYoeEOm2DTOy1mb77o4m5D/wGLHskEhgWu7c8 Y10YHcVAUMMQmwm8n87dw7DIxWxYd8RlvM4i4QncaX/pBeS+Gh7gOI1qaqIkV2LgX0XF 6xuqDb9Y3h6n+t3deExwQMgfMHv3MslWfC0RHa5GSM0+LO9nUeqP89VFe6lgwTVfkWaj RGCg==
X-Gm-Message-State: ALoCoQnUBoqPV6LG1JPcc2wE07Db7Oey32vjDZGQHpHjHXp+dB93IaWwvrYONGb8s9VHbRKHQM08
X-Received: by 10.220.59.138 with SMTP id l10mr4203597vch.59.1410816375558; Mon, 15 Sep 2014 14:26:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.214.4 with HTTP; Mon, 15 Sep 2014 14:25:55 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <5417351F.3050706@bbn.com>
References: <CAHbuEH4Ccn2Z=8kEECzvgjmtshwsFoa-EH_NpkJPos7zirGeaQ@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739439AEC00DB@TK5EX14MBXC292.redmond.corp.microsoft.com> <5416FE10.3060608@bbn.com> <4E1F6AAD24975D4BA5B16804296739439AECCC93@TK5EX14MBXC292.redmond.corp.microsoft.com> <5417351F.3050706@bbn.com>
From: Tim Bray <tbray@textuality.com>
Date: Mon, 15 Sep 2014 14:25:55 -0700
Message-ID: <CAHBU6iuBVwWEzjuVp3kaSVrdedv5eCoxnN24UPGD=1VqTyzvig@mail.gmail.com>
To: Stephen Kent <kent@bbn.com>
Content-Type: multipart/alternative; boundary="001a11c25182e8a3a10503214846"
Archived-At: http://mailarchive.ietf.org/arch/msg/jose/Rubz2mFYHlZHZiYYPfX69V0_M9k
Cc: "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, "secdir@ietf.org" <secdir@ietf.org>, "draft-ietf-jose-json-web-key.all@tools.ietf.org" <draft-ietf-jose-json-web-key.all@tools.ietf.org>, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, Mike Jones <Michael.Jones@microsoft.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] JWK member names, was: SECDIR review of draft-ietf-jose-json-web-key-31
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: Mon, 15 Sep 2014 21:27:08 -0000

On Mon, Sep 15, 2014 at 11:51 AM, Stephen Kent <kent@bbn.com> wrote:

I read the rationale. Is there a good baseline of experience showing that
> JSON parsers are
> not very exploitable today?
>

​Well, increasingly, more or less every Internet facing API is
JSON-over-HTTP; the amount of JSON in circulation is huge. So, nothing in
the world is 100% debugged, but production JSON parsers are among the
better-tested software suites in the world.  It also helps that the JSON
format is very stripped-down and doesn’t provide a very rich attack
surface.​

-- 
- Tim Bray (If you’d like to send me a private message, see
https://keybase.io/timbray)

v2.23.0 | Report a Bug | By Email