<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Checklist on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/checklist/</link><description>Recent content in Checklist on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Fri, 06 Jul 2012 14:34:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/checklist/index.xml" rel="self" type="application/rss+xml"/><item><title>Definitive PHP security checklist</title><link>http://karpoke.ignaciocano.com/2012/07/06/definitive-php-security-checklist/</link><pubDate>Fri, 06 Jul 2012 14:34:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2012/07/06/definitive-php-security-checklist/</guid><description>&lt;blockquote&gt;
&lt;p&gt;There was a recent question about a PHP security checklist on a forum
I frequent, and I’ve decided to write my own comprehensive checklist
to fill the void. There’s something for everyone but the security
expert. In fact, you might find an issue that you never thought about.
Securing PHP web applications would be a better title for this
article.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» &lt;a href="http://www.sk89q.com/2009/08/definitive-php-security-checklist/"&gt;sk89q.com&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>