<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Wed, 22 May 2013 06:35:58 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[DevShed: Securing Your Web Application Against Attacks]]></title>
      <guid>http://www.phpdeveloper.org/news/11254</guid>
      <link>http://www.phpdeveloper.org/news/11254</link>
      <description><![CDATA[<p>
DevShed continues their series focusing on the security of your web application in <a href="http://www.devshed.com/c/a/PHP/Securing-Your-Web-Application-Against-Attacks/">this fifth part</a> of the series. This time they look at preventing attacks on your app via correct authentication.
</p>
<blockquote>
You will probably recall from the last article that I mentioned the existence of two methods of authentication and discussed the first one, which is through an HTML form. In this article, the fifth one in an eight-part series, we'll start with the second method of authentication. We'll also discuss how attackers may gain access to your system.
</blockquote>
<p>
This authentication method uses a simple form to let the user pass in their credentials. Unfortunately, because of its simplicity, this also opens it up to three kinds of attacks - password sniffing, reply attacks and brute force attacks.
</p>]]></description>
      <pubDate>Tue, 21 Oct 2008 08:47:32 -0500</pubDate>
    </item>
  </channel>
</rss>
