Tips & Tricks: Input Filtering, Part 1

Thu, 21 Jul 2005 21:27 UTC

php|architect - July 2005 Tips & Tricks: Input Filtering, Part 1: Why Filter?

by Ben Ramsey
php|architect
July 2005

From the introduction:

This year has seen an increased focus on PHP security, and this is good for the language, developers, and business community. One phrase that comes to mind when discussing secure coding practices is Chris Shiflett’s mantra of ‘filter input, escape output.’ While we know what this means in a general sense, practical examples elude us. Ben Ramsey provides part one of his input filtering series, chock full of code examples.


5 Responses to “Tips & Tricks: Input Filtering, Part 1”

Nice work Ben! I picked up this mag on-line just the other day. Keep up the good work!

Comment by SeeBQ
Sat, 23 Jul 2005 at 17:47 UTC | Permalink

Maybe we should come up with an acronym for that – FIEO. Everyone loves acronyms. :-)

Comment by Chris Shiflett
Thu, 28 Jul 2005 at 19:55 UTC | Permalink

I patented “FIEO” weeks ago ;-)

Comment by Christian
Sat, 30 Jul 2005 at 12:14 UTC | Permalink

Any chance you could find it in yourself to publish outside php|arch since not all of us developers are subscribers, and do not warrent the subscription :eek:

Thank you.

Comment by Les
Sun, 23 Oct 2005 at 9:45 UTC | Permalink

Les, the problem with a technology magazine (any of them, as I understand it) is that the magazine owns the copyright on the articles/columns that authors publish in them. The copyright does not revert back to the author like it does in so many other markets. In short, I don’t have the right to publish my articles anywhere else because I no longer own them.

However, the good folks at php|architect may be willing to work with me on this, as they have done with Chris Shiflett, so I’ll look into it and see what kind of agreement we can come to.

Thanks for your interest.

Comment by Ben Ramsey
Sun, 23 Oct 2005 at 15:12 UTC | Permalink