Re: PHP 5.1
| From: | Ryan King | Date: | Wed, 02 Feb 2005 05:15:42 +0000 |
| Subject: | Re: PHP 5.1 | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-14510@lists.php.net to get a copy of this message | ||
On Feb 1, 2005, at 4:55 PM, Rasmus Lerdorf wrote:
Attachment: [application/pkcs7-signature] smime.p7s
Nick Loeve wrote:This makes me think it would be nice to have a way to test and see if anything was caught by the filters. I guess: if (!(filter(GET,'foo',FILTER_RAW);)) //then something was caught? -ryan -- http://theryanking.com/blogNo, because we don't actually want to lose the raw data. We need to save the raw data internally in PHP and make it available via the filter function. So if a strict default ini filter is enabled you would have something like this: GET /script.php?foo=<xss hack>123 Hello</xss hack> echo $_GET['foo']; Would output: 123 Hello echo filter(GET,'foo',FILTER_RAW); Would output: <xss hack>123 Hello</xss hack> echo filter(GET,'foo',FILTER_NUMBER); Would output: 123Rasmus Lerdorf wrote:Isn't that something you can use mod_security for? I don't know of the availability of that module on a standard host, but on a dedicated server you could install it.I don't actually see it as a per-script thing. Obviously the ini would be per-dir Apache configurable, but I see this as being something set across the board on a dedicated server that defines the security policy of that server.
Attachment: [application/pkcs7-signature] smime.p7s