Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:63078 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72625 invoked from network); 18 Sep 2012 17:17:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Sep 2012 17:17:30 -0000 Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 64.22.89.133 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 64.22.89.133 oxmail.registrar-servers.com Received: from [64.22.89.133] ([64.22.89.133:52351] helo=oxmail.registrar-servers.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 54/E3-07072-9ACA8505 for ; Tue, 18 Sep 2012 13:17:30 -0400 Received: from [192.168.0.200] (5ad4bfa1.bb.sky.com [90.212.191.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by oxmail.registrar-servers.com (Postfix) with ESMTPSA id 17944758083; Tue, 18 Sep 2012 13:17:25 -0400 (EDT) Message-ID: <5058AC72.4050906@ajf.me> Date: Tue, 18 Sep 2012 18:16:34 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Anthony Ferrara CC: Stas Malyshev , =?ISO-8859-1?Q?P=E1draic_Br?= =?ISO-8859-1?Q?ady?= , "internals@lists.php.net" References: <5058A697.30903@sugarcrm.com> <5058A8B8.3070404@sugarcrm.com> <5058A97A.4080900@ajf.me> <5058AABA.1040406@sugarcrm.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------080606090506030207080601" Subject: Re: [PHP-DEV] RFC: Implementing a core anti-XSS escaping class From: ajf@ajf.me (Andrew Faulds) --------------080606090506030207080601 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 18/09/12 18:14, Anthony Ferrara wrote: > Stas, > > On Tue, Sep 18, 2012 at 1:09 PM, Stas Malyshev > wrote: > > Hi! > > > No it's not. A filter removes, but escaping lets the original > content > > pass through unchanged, with the necessary in-band signalling to > make > > sure that its content is not treated as in-band signalling. > > Again, you are confusing particular implementation of a particular > filter with the idea of filtering. Moreover, even existing filters do > not match your description: > > > No, he's not. Filtering and escaping are two very significant concepts > in security. Just because PHP implemented some escaping concepts into > the filter function does not mean that the concerns are co-related. Ah, again you see, I'm confusing things :) In the security context, English language context, and signal processing context, a filter removes. In computer science, but not computer security, it processes. I'm very confused :P -- Andrew Faulds http://ajf.me/ --------------080606090506030207080601--