IETF Logo Mail Archive

Re: [Json] Security considerations

Tim Bray <tbray@textuality.com> Mon, 07 October 2013 03:18 UTC

Return-Path: <tbray@textuality.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68C9321E8133 for <json@ietfa.amsl.com>; Sun, 6 Oct 2013 20:18:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CdK8VgycJ6TE for <json@ietfa.amsl.com>; Sun, 6 Oct 2013 20:18:34 -0700 (PDT)
Received: from mail-vc0-f174.google.com (mail-vc0-f174.google.com [209.85.220.174]) by ietfa.amsl.com (Postfix) with ESMTP id 3E35D21E813B for <json@ietf.org>; Sun, 6 Oct 2013 20:18:34 -0700 (PDT)
Received: by mail-vc0-f174.google.com with SMTP id gd11so2708803vcb.33 for <json@ietf.org>; Sun, 06 Oct 2013 20:18:33 -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:date :message-id:subject:from:to:cc:content-type; bh=5uqfsmD2VtyYjxRkSB3GXs5J0+c0XbqPYXRcSqekSM4=; b=hLA5WUu0AIL/+s6b265BCR5ng3CwJeOQquypbYMgLVOYuPh9Zh2VAyLpMX+yGUwA2M TeRpsaq1q6laRG0xe2wYAAahkVV7anWgKSEa9asxWAadYYbU1z+XIuNeaeBhSwwM3+Lf ZLVE5R5wqVjy3pMI1GDg1rBhdNrlEx6kl986t3LhDAddDDWTqM6kKC3XRXLHPMIvqJoN Y++kfdol759Bdnol9kad7ly25ov++BKuEwMKcEBOdpheyBh82XAP3TX44SGf+yeiPgbQ O6xuEw7mHASx35drKRYd/i7ZsZBuhbbynRhx0BaJQZe2kpNK/M87cmEVP0V38+4Q57sV kLMA==
X-Gm-Message-State: ALoCoQnV14eFrQ8GWECFeuYaVp5FX3ZnWwGGfiSRAndo6O4rHono1E00Mxxywl4nJKfDSQ81kPbp
MIME-Version: 1.0
X-Received: by 10.58.108.74 with SMTP id hi10mr25130802veb.14.1381115913589; Sun, 06 Oct 2013 20:18:33 -0700 (PDT)
Received: by 10.220.174.197 with HTTP; Sun, 6 Oct 2013 20:18:33 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <FCDBFB26-BABB-4D49-A464-BBD68C7FE3B3@vpnc.org>
References: <CAHBU6iuLBDQd1a8D1vJXg4hUUQf6hBgs7vEsXZHLX_nrWE6aRA@mail.gmail.com> <7C4636E2-2819-4FD9-819F-A3594DADA711@tzi.org> <CAChr6Sz1B_1ZLEye=1XA=AiRUuZZ+HBiovC4VK0-aMkjd9O2ZA@mail.gmail.com> <20131007014220.GR7224@mercury.ccil.org> <FCDBFB26-BABB-4D49-A464-BBD68C7FE3B3@vpnc.org>
Date: Sun, 06 Oct 2013 20:18:33 -0700
Message-ID: <CAHBU6isVgBXS=LG6CPgn2-tus5HTgkYoaDc2t8FPsWLBs2BFgA@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary="001a1130ca2e6c63f304e81e1b8b"
Cc: John Cowan <cowan@mercury.ccil.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Security considerations
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Oct 2013 03:18:39 -0000

On Sun, Oct 6, 2013 at 7:37 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> This document will not go there. The IETF rarely (if ever) puts on
> Standards Track "here is a bomb that is likely to be defused".
>

You mean will not cover might-make-you-safe regex, or will not warn of the
dangers of eval()?



>
> It really isn't necessary in this case to add JavaScript-specific code,
> much less code that might be unsafe.
>
> --Paul Hoffman
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>

v2.23.0 | Report a Bug | By Email