<?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>Thu, 24 May 2012 11:48:23 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Marco Tabini's Blog: Security-related bugs are good. No, really!]]></title>
      <guid>http://www.phpdeveloper.org/news/4786</guid>
      <link>http://www.phpdeveloper.org/news/4786</link>
      <description><![CDATA[In <a href="http://blogs.phparch.com/mt/?p=124">his latest entry</a>, <i>Marco Tabini</i> talks about some of the security issues surrounding PHP that have been going around lately, and his take on the situation.
<p>
<quote>
<i>
If you happen to keep a tab on the various posts in the community, you have undoubtedly noted a variety of opinions on the subject-I think that security doesn't belong in the language, Chris <a href="http://shiflett.org/archive/185">has made his point clear</a> and Harry sort-of <a href="http://www.sitepoint.com/blogs/2006/01/24/php-security-dumb-users-or-dumb-apis/">responded to both of us</a>.
<p>
As a community, we are all tasked with ensuring that PHP becomes a better product. And by "community" I really mean everyone-individuals, OSS groups and commercial entities. I think that finally, after so many false starts, we are beginning to do a good job of it, too.
</i>
</quote>
<p>
<a href="http://blogs.phparch.com/mt/?p=124">The post</a> continues on, talking more about the ever-growing trend towards PHP5 and a push forward towards applications written with it with better security and less issues overall...]]></description>
      <pubDate>Fri, 03 Feb 2006 06:36:09 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Chris Shiflett's Blog: Pro PHP Podcast]]></title>
      <guid>http://www.phpdeveloper.org/news/4687</guid>
      <link>http://www.phpdeveloper.org/news/4687</link>
      <description><![CDATA[<i>Chris Shiflett</i> has <a href="http://shiflett.org/archive/182">this post</a> today about the partnership between php|architect and the Pro PHP Podcast.
<p>
<quote>
<i>
You've probably heard the <a href="http://www.marcuswhitney.com/?p=34">good news</a> about the <a href="http://podcast.phparch.com/">Pro PHP Podcast</a>. The guys behind the show (<a href="http://marcuswhitney.com/">Marcus Whitney</a> and <a href="http://blog.phpdeveloper.org/">Chris Cornutt</a>) are joining forces with <a href="http://phparch.com/">php|architect</a> in what should be a good thing for all of us.
<p>
So, I was very happy to hear about the partnership with php|architect, because I know this will let Marcus focus on the show. There are also regular newscasts planned, and Chris is asking, <a href="http://blog.phpdeveloper.org/?p=27">What do you want out of your news</a>?
</i>
</quote>
<p>
Always good to see community support behind a project...and remember, the first show of this new partnership is happening January 27th, an interview with Andi Gutmans that will be broadcast live. <a href="http://www.phparch.com/shop_product.php?itemid=106">Click here</a> to sign up...]]></description>
      <pubDate>Thu, 19 Jan 2006 06:38:32 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Chris Shiflett's Blog: 2005 Highlights]]></title>
      <guid>http://www.phpdeveloper.org/news/4654</guid>
      <link>http://www.phpdeveloper.org/news/4654</link>
      <description><![CDATA[<i>Chris Shiflett</i> has posted <a href="http://shiflett.org/archive/181">this new item</a> on his blog today with his look back at his year in 2005 - both personal and community related.
<p>
<quote>
<i>
In the tradition of my 2003 and 2004 highlights, I'm posting my personal highlights of 2005. As in years past, this is mainly for my own benefit. I hope everyone has a wonderful 2006.
</i>
</quote>
<p>
Some of the more memorable things on his list include:
<ul>
<li>the launch of the <a href="http://phpsec.org/">PHP Security Consortium</a>
<li>the launch of his consulting company, <a href="http://brainbulb.com/">BrainBulb</a>
<li>made numerous speeches
<li>completed his second book, <a href="http://phpsecurity.org/>Essential PHP Security</a>
<li>and launched <a href="http://phpsecurity.org/">PHPDecurity.org</a>, a companion to it
</ul>
<p>
Overall, a great year...he <a href="http://shiflett.org/archive/181">also includes</a> some of the things that he'd like to do in the next year as well (speak at fewer conferences, contribute more to open source, etc). ]]></description>
      <pubDate>Fri, 13 Jan 2006 06:45:52 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Chris Shiflett's Blog: Essential PHP Security - Forms and URLs]]></title>
      <guid>http://www.phpdeveloper.org/news/4549</guid>
      <link>http://www.phpdeveloper.org/news/4549</link>
      <description><![CDATA[<i>Chris Shiflett</i> has <a href="http://shiflett.org/archive/179">a new post</a> on his blog today that points to a sample chapter of his book, "Essential PHP Security", that's been posted over on MySQL's Developer Zone.
<p>
<quote>
<i>
The sample chapter of <a href="http://phpsecurity.org/">Essential PHP Security</a> for <a href="http://dev.mysql.com/">MySQL's Developer Zone</a> is <a href="http://dev.mysql.com/tech-resources/articles/php-security-ch02.php">now available</a>: <a href="http://dev.mysql.com/tech-resources/articles/php-security-ch02.php">Chapter 2, Forms and URLs</a>.
<p>
This chapter discusses form processing and the most common types of attacks that you need to be aware of when dealing with data from forms and URLs. You will learn about attacks such as cross-site scripting (XSS) and cross-site request forgeries (CSRF), as well as how to spoof forms and raw HTTP requests manually. By the end of the chapter, you will not only see examples of these attacks, but also what practices you can employ to help prevent them.
</i>
</quote>
<p>
If you haven't gotten a chance to check out <a href="http://phpsecurity.org/">the book</a>, you definitely should. It's recieved greate reviews by people all over the community, and thought smaller, contains a lion's share of information about PHP security matters...]]></description>
      <pubDate>Thu, 22 Dec 2005 11:00:47 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Chris Shiflett's Blog: Google XSS and Evil Character Encoding]]></title>
      <guid>http://www.phpdeveloper.org/news/4540</guid>
      <link>http://www.phpdeveloper.org/news/4540</link>
      <description><![CDATA[On his blog today, <i>Chris Shiflett</i> has two posts about a problem with Google and a Cross-site Scripting attack that it's vulnerable to.
<p>
From <a href="http://shiflett.org/archive/177">this post</a>:
<quote>
<i>
The recent cross-site scripting (XSS) vulnerability discovered in Google perfectly illustrates why character encoding matters. <a href="http://phpsecurity.org/code/ch01-4">This example</a> demonstrates how to use PHP's htmlentities() with the optional third argument that indicates the character encoding.
</i>
</quote>
<p>
By way of demonstration, he provides a little PHP script that makes a request in a different character encoding than Google can handle. Coupled with the small response from Google, a UTF-7 character sent to certain browsers could be interpreted and executed.
<p>
In <a href="http://shiflett.org/archive/178">this second post</a>, he answers a question from the comments - "how will this effect my site?"
<p>
<quote>
<i>
Rather than offer another vague answer, I decided to provide a very simple proof of concept that demonstrates how character encoding inconsistencies can bite you. Google's vulnerability has of course been fixed, but with a simple PHP script, we can reproduce the situation.
</i>
</quote>
<p>
<a href="http://shiflett.org/archive/178">The script</a>, though escaped, still causes a Javascript popup box to show when the page is loaded - all due to a lack of improper character encoding handling...]]></description>
      <pubDate>Thu, 22 Dec 2005 06:19:39 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[John Cox's Blog:  Security Blunders]]></title>
      <guid>http://www.phpdeveloper.org/news/4533</guid>
      <link>http://www.phpdeveloper.org/news/4533</link>
      <description><![CDATA[In <a href="http://wyome.com/index.php?module=articles&func=display&ptid=10&aid=492">his latest post</a> today, <i>John Cox</i> takes a look at one of the latest posts from the SitePoint PHP blog - the <a href="http://www.sitepoint.com/article/php-security-blunders">Top 7 PHP Security Blunders</a>.
<p>
<quote>
<i>
This morning I read the <a href="http://www.sitepoint.com/article/php-security-blunders">Top 7 PHP Security Blunders</a> which contained (at least in my mind) a few questionable comments about PHP security. Luckily for the early readers of the article, there was a very long comment by <a href="http://shiflett.org/>Chris Shiflett</a> trailing the article. The <a href="http://www.sitepoint.com/forums/showpost.php?p=2374757&postcount=9">comments</a> were a very nice critique of the article which also corrects a few obvious mistakes within the article itself. 
<p>
The comments have now been pushed off the main article to the forum, (which is a shame) but as a developer, you would be doing yourself a disservice by not also taking the time to read the counter-point. They are insightful without being inflammatory.
</i>
</quote>
<p>
The comments by <i>Chris</i> that he makes reference to can be found <a href="http://www.sitepoint.com/forums/showpost.php?p=2374757&postcount=9">here in the SitePoint forums</a>...]]></description>
      <pubDate>Wed, 21 Dec 2005 07:08:07 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[CodeSnipers.com: Interview with Chris Shiflett]]></title>
      <guid>http://www.phpdeveloper.org/news/4503</guid>
      <link>http://www.phpdeveloper.org/news/4503</link>
      <description><![CDATA[From CodeSnipers.com today, there's <a href="http://codesnipers.com/?q=node/193&title=">this new post</a> with an interview with the author of Essential PHP Security, <i>Chris Shiflett</i>.
<p>
<quote>
<i>
This is the third in a series of interviews we're making available to the CodeSnipers community. We have been working to track down people who we thought had something valuable to say about the software development community, tools, practices, or direction. Some of the names you will recognize immediately, others you've probably never heard of, but all of them have made an impact in one way or another. Without further delay... we have Chris Shiflett author of Essential PHP Security.
</i>
</quote>
<p>
As <i>Chris</i> notes in <a href="http://shiflett.org/archive/174">his blog entry</i>, they talk about everything - from his book to his involvement in the PHP community...]]></description>
      <pubDate>Thu, 15 Dec 2005 06:45:45 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Chris Shiflett's Blog: PHPSecurity.org Launches]]></title>
      <guid>http://www.phpdeveloper.org/news/4450</guid>
      <link>http://www.phpdeveloper.org/news/4450</link>
      <description><![CDATA[In an effort to help increase the security awareness (more than he already has), <i>Chris Shiflett</i> has created a companion site for his O'Reilly book "Essential PHP Security" - <a href="http://phpsecurity.org/">PHPSecurity.org</a>.
<p>
<quote>
<i>
<a href="http://phpsecurity.org/">PHPSecurity.org</a>, the companion web site for my new book, <a href="http://phpsecurity.org/">Essential PHP Security</a>, is now online. Many thanks to <a href="http://slash7.com/">Amy Hoy</a> for the excellent design!
<p>
I've included the <a href="http://phpsecurity.org/contents">table of contents</a>, the (unfortunate) <a href="http://phpsecurity.org/errata">errata</a>, some <a href="http://phpsecurity.org/reviews">reviews</a>, and the <a href="http://phpsecurity.org/code">code repository</a>. 
</i>
</quote>
<p>
He also <a href="http://shiflett.org/archive/172">notes</a> that, while there are partial examples in the book, there is no complete example that could be used to do anything malicious (the parts are there, obviously, but just not in once place). Overall, though, he says that the book has been doing well, and has gotten a very warm reception from the community - hence the expansion out to the <a href="http://phpsecurity.org/">new site</a>...]]></description>
      <pubDate>Wed, 07 Dec 2005 07:03:43 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Davey Shafik's Blog: Review - Essential PHP Security by Chris Shiflett]]></title>
      <guid>http://www.phpdeveloper.org/news/4295</guid>
      <link>http://www.phpdeveloper.org/news/4295</link>
      <description><![CDATA[On his blog today, <i>Davey Shafik</i> has <a href="http://pixelated-dreams.com/archives/195-Review-Essential-PHP-Security-by-Chris-Shiflett.html">this review</a> of <i>Chris Shiflett</i>'s Essential PHP Security guide from O'Reilly.
<p>
<quote>
<i>
I was fortunate enough to receive a copy of <a href="http://shiflett.org/">Chris Shiflett's</a> book, <a href="http://www.amazon.com/exec/obidos/ASIN/059600656X/ref%3Dnosim/chrisshiflett-20">Essential PHP Security</a> published by <a href="http://oreilly.com/">O'Reilly</a>.
<p>
Chris does an excellent job dissecting and explaining each of the 8 major security topics he covers in his book, first outlines what exactly the problem is, how easily it is to fall into the trap of making your code vulnerable to it, and how it is generally exploited. He then goes on to tell you how you can be sure that you are not vulnerable in the future.
</i>
</quote>
<p>
He <a href="http://pixelated-dreams.com/archives/195-Review-Essential-PHP-Security-by-Chris-Shiflett.html">also notes</a> that the "Essential" in the name is quite appropriate, and that if you purchase one PHP security book, make <a href="http://www.amazon.com/exec/obidos/ASIN/059600656X/ref%3Dnosim/chrisshiflett-20">this the one</a>...]]></description>
      <pubDate>Mon, 14 Nov 2005 06:11:34 -0600</pubDate>
    </item>
  </channel>
</rss>

