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 8A1F121E8145 for <json@ietfa.amsl.com>;
 Sun,  6 Oct 2013 21:09:07 -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=[AWL=-0.000,
 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 0qgMm9Yaqphw for
 <json@ietfa.amsl.com>; Sun,  6 Oct 2013 21:09:02 -0700 (PDT)
Received: from mail-ve0-f169.google.com (mail-ve0-f169.google.com
 [209.85.128.169]) by ietfa.amsl.com (Postfix) with ESMTP id D739221E813D for
 <json@ietf.org>; Sun,  6 Oct 2013 21:09:00 -0700 (PDT)
Received: by mail-ve0-f169.google.com with SMTP id db12so3624493veb.28 for
 <json@ietf.org>; Sun, 06 Oct 2013 21:09:00 -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=aRTPeEcPoPaxk4d9spFHgXznAH1trsZdxxZtMvEoHi0=;
 b=f6pNR4PL8oa6CglWrWInhA2uUyvIcVgJ+vfaW5X2Pioe988h0F+vizjok5J2eQ1/0M
 0yvfCjbmEi3tNTuvkCCtNjntb0dXs50yP9hl3I+S8xkBLsJwPDWaShRQ2YHduEg3IkpV
 XvvodUphrcTJGpDT4WjLA1U1nP6rDXWLSCGi06/DFQXkTmQKDv6YqmOD7fEzQkhCg6Vk
 j9GikQS1n71subqv33V63e09zGJAMUA24oe0UaHWYp60QpsOXCOaS7TKvr+1Ug77Edru
 9ZGm0CxRoefNspMDErHUd4wek+KFQ6zFzM9X9OeAtAYgGDbISUoicwBSyXhLxIuXPDEO 4vzQ==
X-Gm-Message-State: ALoCoQlnIFJsLCyov9noowhaO0b8U19tvRbvDftWD0Z5y0O5td84rthw9cQnSBTZQh9goELMcAUN
MIME-Version: 1.0
X-Received: by 10.52.32.37 with SMTP id f5mr20290248vdi.17.1381118940130;
 Sun, 06 Oct 2013 21:09:00 -0700 (PDT)
Received: by 10.220.174.197 with HTTP; Sun, 6 Oct 2013 21:09:00 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <8DD26019-C037-4E66-ADD8-AE01832E5EE1@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>
 <CAHBU6isVgBXS=LG6CPgn2-tus5HTgkYoaDc2t8FPsWLBs2BFgA@mail.gmail.com>
 <8DD26019-C037-4E66-ADD8-AE01832E5EE1@vpnc.org>
Date: Sun, 6 Oct 2013 21:09:00 -0700
Message-ID: <CAHBU6iup96di+EQ4uUV-s2EhDbh1tmerZYF10nbOCxNz3enZNw@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary=bcaec51d2552d1c47a04e81ecf6d
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 04:09:07 -0000

--bcaec51d2552d1c47a04e81ecf6d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

What is the argument against including a conventional warning against a
plausible-but-dangerous practice?  The only one I can think of is =E2=80=9C=
everyone
already knows that=E2=80=9D which doesn=E2=80=99t seem very strong to me.


On Sun, Oct 6, 2013 at 8:19 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> On Oct 6, 2013, at 8:18 PM, Tim Bray <tbray@textuality.com> wrote:
>
> > You mean will not cover might-make-you-safe regex, or will not warn of
> the dangers of eval()?
>
> Correct.
>
> --Paul HOffman
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>

--bcaec51d2552d1c47a04e81ecf6d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">What is the argument against including a conventional warn=
ing against a plausible-but-dangerous practice?=C2=A0 The only one I can th=
ink of is =E2=80=9Ceveryone already knows that=E2=80=9D which doesn=E2=80=
=99t seem very strong to me.<br>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sun,=
 Oct 6, 2013 at 8:19 PM, Paul Hoffman <span dir=3D"ltr">&lt;<a href=3D"mail=
to:paul.hoffman@vpnc.org" target=3D"_blank">paul.hoffman@vpnc.org</a>&gt;</=
span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Oct 6, 2013, at 8:18 PM=
, Tim Bray &lt;<a href=3D"mailto:tbray@textuality.com">tbray@textuality.com=
</a>&gt; wrote:<br>

<br>
&gt; You mean will not cover might-make-you-safe regex, or will not warn of=
 the dangers of eval()?<br>
<br>
</div>Correct.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--Paul HOffman<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5">_____________________=
__________________________<br>
json mailing list<br>
<a href=3D"mailto:json@ietf.org">json@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/json" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/json</a><br>
</div></div></blockquote></div><br></div>

--bcaec51d2552d1c47a04e81ecf6d--
