<?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>Mon, 20 May 2013 17:48:03 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[DevShed: Hackers Compromise PHP Sites to Launch Attacks]]></title>
      <guid>http://www.phpdeveloper.org/news/18911</guid>
      <link>http://www.phpdeveloper.org/news/18911</link>
      <description><![CDATA[<p>
According to <a href="http://www.devshed.com/c/a/PHP/Hackers-Compromise-PHP-Sites-to-Launch-Attacks-93656/">this new post</a> on DevShed, there have been several targeted attacks against U.S. bank websites (DDoS), some of which involved the compromise of PHP-based applications.
</p>
<blockquote>
Once the hackers got into the PHP-based websites, they inserted toolkits to turn them into launch pads for their distributed denial-of-service attacks. Hackers then launched the attacks on banks by connecting directly to the compromised PHP-based websites and sending them commands, or took advantage of intermediate servers, proxies or scripts to make the websites do their bidding. InformationWeek lists three attack tools used by the hackers: KamiKaze, AMOS, and the "itsokaynoproblembro" toolkit, also known as Brobot.
</blockquote>
<p>
Several major banks have been targeted including Bank of America, JP Morgan/Chase, HSBC and Well Fargo. The main problem was out-of-date software running on the site containing known security issues the attackers could exploit to install their own software.
</p>
<blockquote>
If a hacker can break into a PHP-based website to use it as a staging area for an attack on a different website, they can also use that website to store stolen information. InformationWeek cited the example of the Eurograbber attack campaign, revealed earlier this month. The gang involved in that campaign stole $47 million from more than 30,000 corporate and private banking customers - and used PHP-based websites into which they hacked to store stolen information.
</blockquote>]]></description>
      <pubDate>Tue, 18 Dec 2012 12:07:35 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Developer Tutorials Blog: Five Wordpress Tips for Power Users]]></title>
      <guid>http://www.phpdeveloper.org/news/10127</guid>
      <link>http://www.phpdeveloper.org/news/10127</link>
      <description><![CDATA[<p>
On the Developer Tutorials Blog today, there's a <a href="http://www.developertutorials.com/blog/general/five-wordpress-tips-for-power-users-166/">new post</a> aimed at WordPress users to help them on the path to becoming "power users" with five tips.
</p>
<blockquote>
If you're a wordpress power user, you'll inevitably have some questions about how you can improve your blog or add new features. Here are five tips that will make life easier for people wanting to maximize their use of Wordpress.
</blockquote>
<p>
<a href="http://www.developertutorials.com/blog/general/five-wordpress-tips-for-power-users-166/">The list</a> is:
</p>
<ul>
<li>Quickly Find Page/Post ID
<li>Custom Front Page
<li>Password Protect Wordpress
<li>Protect from the 'Digg Efect' with HTML
<li>Stop Hackers
</ul>
<p>
Each of them with their own explanations (and links to other resources detailing how they're done).
</p>]]></description>
      <pubDate>Wed, 07 May 2008 07:57:58 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Community News: Perspectives on Google Code Search (Help or Hinder?)]]></title>
      <guid>http://www.phpdeveloper.org/news/6438</guid>
      <link>http://www.phpdeveloper.org/news/6438</link>
      <description><![CDATA[<p>
Everyone in the PHP community (as is probably true all around the web) is buzzing about the new offering from Google - the <a href="http://www.google.com/codesearch">Google Code Search</a>. In the PHP community, the ones talking about it so far include:
<ul>
<li><i>Chris Shiflett</i>'s <a href="http://shiflett.org/archive/269">look at the security aspect</a> of the search
<li><i>Ilia Alshanetsky</i>'s <a href="http://ilia.ws/archives/133-Google-Code-Search-Hackers-best-friend.html">take on the search</a> as it possibly being a hacker's good friend
<li><i>Pierre-Alain Joye</i>'s searches for macros and the term "virtual_file_ex"
<li><i>Harry Fuecks'</i> <a href="http://www.sitepoint.com/blogs/2006/10/06/oh-dear/">own search</a> for superglobal-related issues
<li><i>Ivo Jansch</i>'s happy <a href="http://www.achievo.org/blog/archives/48-Exposing-programming-frustrations-with-Google-Code-Search.html">look into frustrations</a> other developers have had (ex. <a href="http://www.google.com/codesearch?q=fuck+customer">this search</a>)
<li><i>Martin Brotzeller</i>'s <a href="http://blog.thinkphp.de/archives/151-Code-Inclusions-on-a-Silver-Plate.html">comments</a> on the new tool
</ul>
</p>
<p>
Check out <a href="http://www.google.com/codesearch">this handy tool</a> and see what you think. Does it provide too much access to code that needs to stay out of hacker's hands? Or does it promote the "open" in open source better than most of the tools out there?
</p>]]></description>
      <pubDate>Fri, 06 Oct 2006 08:21:00 -0500</pubDate>
    </item>
  </channel>
</rss>
