Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72154 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85958 invoked from network); 3 Feb 2014 22:44:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Feb 2014 22:44:50 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.41 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.41 mail-la0-f41.google.com Received: from [209.85.215.41] ([209.85.215.41:39393] helo=mail-la0-f41.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C6/6E-35654-1EB10F25 for ; Mon, 03 Feb 2014 17:44:49 -0500 Received: by mail-la0-f41.google.com with SMTP id mc6so6038847lab.0 for ; Mon, 03 Feb 2014 14:44:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=uCzwkL73SvuJzOz2ev9641V41SUrwfAZjLvlIgQbLII=; b=Znhuhksf5NiUuC1FDufQorTugCkL8Hgi2RHQTIn+T1s/NJuVSVTzZSGst6kxWW8/fR Yvll0e+dbg6zjQiaP6M/CIcdkd4qiiEg1Xcf2UHBMe+mpVsdwV06uzVZshYb10RN0E84 2UWPtoamYnTgmd6yf6zBxz/soORDHiO0fxe2fVQHWyFZlkewD25QPF2RFzFpTnHNUERC j1Ns87Le3E8VuieKHzvLczeNRuRMpayix0a3WYmwtCJLVUVi0WAY1ezJ2PndXGhnWQp3 kqMBN3EnEz9w/1EOFa4LNW2BX5ITGZJ5mzL5jrMF0YiH7E474AyvHQX6/6YcHybM89vi fNZA== X-Received: by 10.112.168.104 with SMTP id zv8mr11215826lbb.5.1391467486184; Mon, 03 Feb 2014 14:44:46 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.199.37 with HTTP; Mon, 3 Feb 2014 14:44:05 -0800 (PST) In-Reply-To: References: <52EDBB30.3070209@ajf.me> <52EE1C2B.7030702@sugarcrm.com> <52EF50B6.1030404@sugarcrm.com> <52F014C3.4060007@sugarcrm.com> Date: Tue, 4 Feb 2014 07:44:05 +0900 X-Google-Sender-Auth: uIJ2fL-etr1a6VjZ-KdTxkb1-rg Message-ID: To: =?UTF-8?Q?P=C3=A1draic_Brady?= Cc: Stas Malyshev , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a11c3490a3b0d1f04f18845ee Subject: Re: [PHP-DEV] [RFC] Improve HTML escape From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11c3490a3b0d1f04f18845ee Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi all, On Tue, Feb 4, 2014 at 7:37 AM, Yasuo Ohgaki wrote: > On Tue, Feb 4, 2014 at 7:31 AM, P=C3=A1draic Brady wrote: > >> While I'm dubious about forward slash escaping myself and think it >> might have been OWASP veering into overkill, >> > > Yes they are. They are very conservative to security. > For example, they suggest to escape almost all char by applying > HEX escape for JavaScript string literals. > > It may be too much, but I'm sure it's more secure. > If anyone interested in PHP implementation of OWASP suggested JavaScript string literal escape. This is my blog for it. http://blog.ohgaki.net/javascript-string-escape It's written in Japanese. You may recognize PHP code and use google translate or like if you would like to read content. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11c3490a3b0d1f04f18845ee--