Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:63076 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 69863 invoked from network); 18 Sep 2012 17:11:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Sep 2012 17:11:55 -0000 Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; 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:48016] helo=oxmail.registrar-servers.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 94/43-07072-B5BA8505 for ; Tue, 18 Sep 2012 13:11:55 -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 A2EDC7580D4; Tue, 18 Sep 2012 13:11:51 -0400 (EDT) Message-ID: <5058AB28.6070303@ajf.me> Date: Tue, 18 Sep 2012 18:11:04 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Stas Malyshev CC: Anthony Ferrara , =?ISO-8859-1?Q?P=E1draic_Bra?= =?ISO-8859-1?Q?dy?= , "internals@lists.php.net" References: <5058A697.30903@sugarcrm.com> <5058A8B8.3070404@sugarcrm.com> <5058A97A.4080900@ajf.me> <5058AABA.1040406@sugarcrm.com> In-Reply-To: <5058AABA.1040406@sugarcrm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RFC: Implementing a core anti-XSS escaping class From: ajf@ajf.me (Andrew Faulds) On 18/09/12 18:09, 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: > FILTER_SANITIZE_ENCODED, FILTER_SANITIZE_MAGIC_QUOTES, > FILTER_SANITIZE_SPECIAL_CHARS, FILTER_SANITIZE_FULL_SPECIAL_CHARS, > FILTER_SANITIZE_STRING, FILTER_CALLBACK > > But in general, look at implementation of filters anywhere - like Apache > filters or IIS filters - nowhere it is said that filter can only remove > data. Ah, sorry, I think I'm confusing the standard English language meaning of filter with regards to the physical device or signal processing, with the meaning in the field of computer science etc. -- Andrew Faulds http://ajf.me/