<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0"
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>Odynia.org Blog - PHP</title>
    <link>http://blog.odynia.org/</link>
    <description>..</description>
    <dc:language>en</dc:language>
    
    <generator>Serendipity 0.9.1 - http://www.s9y.org/</generator>
    <pubDate>Wed, 28 Jun 2006 18:17:52 GMT</pubDate>

    <image>
        <url>http://blog.odynia.org/templates/wow/img/s9y_banner_small.png</url>
        <title>RSS: Odynia.org Blog - PHP - ..</title>
        <link>http://blog.odynia.org/</link>
        <width>100</width>
        <height>21</height>
    </image>
<item>
    <title>PHP Security</title>
    <link>http://blog.odynia.org/archives/17-PHP-Security.html</link>
<category>PHP</category>    <comments>http://blog.odynia.org/archives/17-PHP-Security.html#comments</comments>
    <wfw:comment>http://blog.odynia.org/wfwcomment.php?cid=17</wfw:comment>
    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://blog.odynia.org/rss.php?version=2.0&amp;type=comments&amp;cid=17</wfw:commentRss>
    <author>nospam@example.com (Robert Amos)</author>
    <content:encoded>
&lt;div&gt;It seems that once again people are trying to spread Fear Uncertainty and Doubt (FUD) about the security of PHP. The article &lt;a href=&quot;http://www.owasp.org/index.php/PHP_Top_5&quot;&gt;http://www.owasp.org/index.php/PHP_Top_5&lt;/a&gt; lists what they consider to be PHP security faults.&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;This is simply not true. None of the faults listed here are actually PHP-specific. The items they list could occur on any programming language if the programmer was sufficiently inexperienced. Further, any and all of the faults have been made harder to access by recent versions of PHP.&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;The article does make for a good read though, on some of the basic security practices you should undertake on any language, and would likely have been well received if not worded in such a manner that it could be perceived as an attack &lt;img src=&quot;http://blog.odynia.org/templates/wow/img/emoticons/smile.png&quot; alt=&quot;:-)&quot; style=&quot;display: inline; vertical-align: bottom;&quot; class=&quot;emoticon&quot; /&gt;&lt;/div&gt;
&lt;Br /&gt;
&lt;div&gt;Remember though, a programming language is only as secure as the person using it. Read up on your security practices and you'll be right. Pay attention to security announcements, most major open source projects have them in an easy to access place, and always keep your software uptodate with patches!&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;-bok&lt;/div&gt;    </content:encoded>
                
    <pubDate>Thu, 29 Jun 2006 04:08:47 +1000</pubDate>
    <guid isPermaLink="false">http://blog.odynia.org/archives/17-guid.html</guid>
    </item>
</channel>
</rss>
