<?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, 19 Jun 2013 01:25:37 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[php|architect: Pro::PHP Podcast - Interview with Ed Finkler]]></title>
      <guid>http://www.phpdeveloper.org/news/7718</guid>
      <link>http://www.phpdeveloper.org/news/7718</link>
      <description><![CDATA[<p>
In a new installation of the <a href="http://podcast.phparch.com">Pro::PHP Podcast</a> just released, <i>Paul Reinheimer</i> sits down and talks with <i>Ed Finkler</i>, "web and security archive administrator".
</p>
<p>
<i>Ed Finkler</i> is also a primary developer on the <a href="http://phpsec.org/projects/phpsecinfo/">PHPSecInfo</a> project, an effort to help bring a baseline of security to developers and their applications:
</p>
<blockquote>
PhpSecInfo provides an equivalent to the <a href="http://php.net/phpinfo">phpinfo()</a> function that reports security information about the PHP environment, and offers suggestions for improvement. It is not a replacement for secure development techniques, and does not do any kind of code or app auditing, but can be a useful tool in a multilayered security approach.
</blockquote>
<p>
Check out some of <i>Ed</i>'s own comments about the interview in this <a href="http://blog.funkatron.com/archives/general/im-interviewed-on-the-prophp-podcast/">new blog entry</a>.
</p>]]></description>
      <pubDate>Thu, 26 Apr 2007 14:08:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Ed Finkler's Blog: Slides from PHPSecInfo Presentation]]></title>
      <guid>http://www.phpdeveloper.org/news/7486</guid>
      <link>http://www.phpdeveloper.org/news/7486</link>
      <description><![CDATA[<p>
<i>Ed Filnker</i> has posted <a href="http://funkatron.com/wp/archives/php/slides-from-phpsecinfo-presentation/">a note about</a> the slides that he presented as a part of the 8th Annual <a href="http://www.cerias.purdue.edu/symposium">CERIAS Information Security Symposium</a>.
</p>
<p>
<a href="http://funkatron.com/wp/wp-content/defending-web%20applications-with-PHPSecInfo.pdf">The presentation</a> [pdf] looks at the state of PHP development, the parties involved (including the "deployer") and the use of the <a href="http://phpsec.org/projects/phpsecinfo/">PHPSecInfo application</a> to help said "deployer" find issues they might miss otherwise. Of course, there's also a section on getting PHPSecInfo up and working on your system (you can unzip, right?) and other add-ons you can use to help avoid questions down the line (like the use of the  Zend_Environment security module in the Zend Framework to test security).
</p>
<p>
Check out <a href="http://funkatron.com/wp/wp-content/defending-web%20applications-with-PHPSecInfo.pdf">the PDF here</a> and keep an eye on <a href="http://funkatron.com/wp/">his blog</a> for an upcoming video of the presentation.
</p>
<p>
<b>UPDATE:</b> he's also <a href="http://funkatron.com/wp/archives/php/audio-from-phpsecinfo-presentation/">posted the audio</a> for the presentation as well - <a href="http://funkatron.com/wp/wp-content/Defending%20Web%20Applications%20With%20PHPSecInfo.mp3">grab the mp3</a>.
</p>]]></description>
      <pubDate>Thu, 22 Mar 2007 11:22:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Zend Developer Zone: PHP Security Tip #13]]></title>
      <guid>http://www.phpdeveloper.org/news/7464</guid>
      <link>http://www.phpdeveloper.org/news/7464</link>
      <description><![CDATA[<p>
In the <a href="http://devzone.zend.com/node/view/id/1833">latest security tip</a> from the Zend Developer Zone, <i>Cal Evans</i> points out a tool previously mentioned in passing that he feels deserves its own post - <a href="http://phpsec.org/projects/phpsecinfo/">PHPSecInfo</a>.
</p>
<blockquote>
<a href="http://phpsec.org/projects/phpsecinfo/">PHPSecInfo</a> is a great tool to use to keep an eye on your production environment. It was written by Ed Finkler of <a href="http://www.cerias.purdue.edu/">CERIAS</a>, the Center for Education and Research in Information Assurance and Security at Purdue University. It is officially a project of the <a href="http://phpsec.org/">PHP Security Consortium</a>.
</blockquote>
<p>
The <a href="http://phpsec.org/projects/phpsecinfo/">tool</a> allows you to easily run a security audit against your system and find the issues in a familiar phpinfo() style of result. Remember, it's a starting place - not an ending one. Security is more than just running a script to check once and a while.
</p>]]></description>
      <pubDate>Tue, 20 Mar 2007 12:17:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Ed Finkler's Blog: PHPSecInfo v0.2 now Available]]></title>
      <guid>http://www.phpdeveloper.org/news/7384</guid>
      <link>http://www.phpdeveloper.org/news/7384</link>
      <description><![CDATA[<p>
The latest version of the popular (and simple) PHP security audit tool, PHPSecInfo, has <a href="http://funkatron.com/wp/archives/php/phpsecinfo-v02-now-available/">been released</a> - version 0.2.
</p>
<p>
The major changes in <a href="http://phpsec.org/projects/phpsecinfo/phpsecinfo.zip">this version</a> [zip] include:
<ul>
<li>"More info" links to give you details on the specified issue
<li>CSS/layout changes to make understanding the results simpler
<li>a new test - PhpSecInfo_Test_Session_Save_Path
<li>and more...
</ul>
Check out <a href="http://phpsec.org/projects/phpsecinfo/CHANGELOG">the Changelog</a> for complete information on the update or just head over and <a href="http://phpsec.org/projects/phpsecinfo/phpsecinfo.zip">download it now</a>.
</p>
]]></description>
      <pubDate>Mon, 05 Mar 2007 13:39:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Zend Developer Zone: PHPSecInfo: New release (0.1.2), new plans]]></title>
      <guid>http://www.phpdeveloper.org/news/6976</guid>
      <link>http://www.phpdeveloper.org/news/6976</link>
      <description><![CDATA[<p>
In <a href="http://devzone.zend.com/node/view/id/1404">a new article</a> on the Zend Developer Zone, <i>Ed Finkler</i> talks a bit about the newly released version of the PHPSecInfo package (<a href="http://phpsec.org/projects/phpsecinfo/">version 0.1.2</a>) and what some of the future plans for it are.
</p>
<blockquote>
New release, new plans! First off, a new build of PHPSecInfo is out. Version 0.1.2, build 20061218. Per usual, get your new version from <a href="http://phpsec.org/projects/phpsecinfo/">http://phpsec.org/projects/phpsecinfo/</a>.
</blockquote>
<p>
New features include:
<ul>
<li>Code is now licensed under 'New BSD' license. See LICENSE
<li>fix bug in post_max_size check where upload_max_size value was being checked
<li>Now providing an md5 hash for releases
</ul>
And some of the plans for the future include more detailed test results, a web-based "glossary" of howtos on fixing problems, and more tests for more cases.
</p>
<p>
If you'd like to contribute tests or other resources to the project, head over to <a href="http://phpsec.org/projects/phpsecinfo/">its homepage</a> and let them know.
</p>]]></description>
      <pubDate>Wed, 27 Dec 2006 11:37:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Zend Developer Zone: Ed Finkler Talks About PHPSecInfo]]></title>
      <guid>http://www.phpdeveloper.org/news/6549</guid>
      <link>http://www.phpdeveloper.org/news/6549</link>
      <description><![CDATA[<p>
<i>Cal Evans</i> over on the Zend Developer Zone has another of his infamous (well, okay - not infamous, but definitely good) interviews with people all around the PHP community. This time, it's <a href="http://devzone.zend.com/node/view/id/1099">a chat</a> with <i>Ed Finkler</i>, a developer over at <a href="http://www.cerias.purdue.edu/">CERIAS</a> concerning the new security tool designed to help even the security-clueless to protect themselves and their system.
</p>
<blockquote>
Intrigued as much by this project, as I was by the fact that Ed wrote me and told me it was time for me to interview him, I called Ed and we talked about the project.
</blockquote>
<p>
They <a href="http://devzone.zend.com/node/view/id/1099">talk about</a> where the idea for the tool came from, one of the targets for the use of the project (those on shared hosting), and the mention that it is modular in design and they are more than happy to have developers work up tests to be sure things are working 100% correctly.
</p>]]></description>
      <pubDate>Mon, 23 Oct 2006 09:37:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[PHP Security Consortium: New Product Launch - PHPSecInfo]]></title>
      <guid>http://www.phpdeveloper.org/news/6543</guid>
      <link>http://www.phpdeveloper.org/news/6543</link>
      <description><![CDATA[<p>
<i>Chris Shiflett</i> has announced (via the phpsec.org mailing list) a new project to help make PHp installations safer in a simple, easy-to-use package - <a href="http://phpsec.org/projects/phpsecinfo/">PHPSecInfo</a>.
</p>
<blockquote>
<p>
Ed Finkler of the PHP Security Consortium has launched a new project to
help developers and system administrators audit PHP environments.
PHPSecInfo  provides a simple-to-use security audit system for the PHP
environment, with a look and feel similar to that of the phpinfo()
function.
</p>
<p>
PHPSecInfo currently has a suite of 16 tests. Interested PHP developers
are encouraged to propose and write new tests for consideration as well
as help refine the existing test suite. You can find contact information
for Ed Finkler and any member of the PHP Security Consortium online at <a href="http://phpsec.org/contact/">http://phpsec.org/contact/</a>.
</p>
</blockquote>
<p>
The development of the project is being partially sponsored by CERIAS at Purdue University. There's <a href="http://phpsec.org/projects/phpsecinfo/">an example</a> of the output from the script and a download dated for the beginning of August. Contributions are welcome and accepted, especially in certain areas like documentation, test writing, suggestions, and feedback.
</p>]]></description>
      <pubDate>Fri, 20 Oct 2006 10:30:08 -0500</pubDate>
    </item>
  </channel>
</rss>
