<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Technosailor - Latest Comments in Understanding Implications of WordPress Plugin Security</title><link>http://technosailor.disqus.com/</link><description></description><atom:link href="https://technosailor.disqus.com/understanding_implications_of_wordpress_plugin_security/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sun, 24 Sep 2006 18:42:59 -0000</lastBuildDate><item><title>Re: Understanding Implications of WordPress Plugin Security</title><link>http://technosailor.com/2006/09/23/understanding-implications-of-wordpress-plugin-security/#comment-1033770</link><description>&lt;p&gt;Perhaps it should be suggested to plugin authors that they request a security review via the forum or IRC? I'm not sure about the forum as I don't participate, but I know there are more than enough people who can check plugin security on the wp-hackers list and in #wordpress on freenode.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew K.</dc:creator><pubDate>Sun, 24 Sep 2006 18:42:59 -0000</pubDate></item><item><title>Re: Understanding Implications of WordPress Plugin Security</title><link>http://technosailor.com/2006/09/23/understanding-implications-of-wordpress-plugin-security/#comment-1033769</link><description>&lt;p&gt;This is why I keep my plugins as simple as possible. Obviously it's not possible to prevent everything in advance, but XSS and the like are low-hanging fruit: anybody writing code should understand them and be able to defend their code from them.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Hampton</dc:creator><pubDate>Sat, 23 Sep 2006 14:05:33 -0000</pubDate></item></channel></rss>