<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Google hearts me again</title>
	<atom:link href="http://www.accphotos.com/blog/2008/01/28/google-hearts-me-again/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.accphotos.com/blog/2008/01/28/google-hearts-me-again/</link>
	<description>blog about ACC sports and photography</description>
	<pubDate>Tue, 06 Jan 2009 09:37:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Christopher Blunck</title>
		<link>http://www.accphotos.com/blog/2008/01/28/google-hearts-me-again/comment-page-1/#comment-3787</link>
		<dc:creator>Christopher Blunck</dc:creator>
		<pubDate>Mon, 28 Jan 2008 19:40:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.accphotos.com/blog/2008/01/28/google-hearts-me-again/#comment-3787</guid>
		<description>Wow Peyton, I'm sorry to hear that.  I'm not at all surprised it happened to you though.  I'm sure your site (http://www.accphotos.com/) receives a ton of traffic, and those sites tend to be the ones that people go after.

I try to stay out of hosting public sites unless it's just static pages.  Apache is pretty resistant to attack, but every now and then a new vulnerability is discovered.  It's difficult to keep up to date with all the latest patches, and I like being able to pay people more qualified than me to maintain something.

A few weeks ago we installed MySQL server on an older Linux server (I think it was running Fedora 5).  Somebody accidentally set it up to listen on all network interfaces rather than localhost.  About 11 hours later somebody overpowered the MySQL server and compromised the server.  From there they launched a bunch of attacks against other networks and started spewing out spam.  Our subnet was blackholed by a bunch of networks and our SMTP servers (google) were on the blacklist by several spam houses.

It took us several weeks before we had fully recovered.  It was such a pain in the neck.  From now on we try to rely on others to host our infrastructure.

I'm happy you hear you climbed back into Google's index.</description>
		<content:encoded><![CDATA[<p>Wow Peyton, I&#8217;m sorry to hear that.  I&#8217;m not at all surprised it happened to you though.  I&#8217;m sure your site (http://www.accphotos.com/) receives a ton of traffic, and those sites tend to be the ones that people go after.</p>
<p>I try to stay out of hosting public sites unless it&#8217;s just static pages.  Apache is pretty resistant to attack, but every now and then a new vulnerability is discovered.  It&#8217;s difficult to keep up to date with all the latest patches, and I like being able to pay people more qualified than me to maintain something.</p>
<p>A few weeks ago we installed MySQL server on an older Linux server (I think it was running Fedora 5).  Somebody accidentally set it up to listen on all network interfaces rather than localhost.  About 11 hours later somebody overpowered the MySQL server and compromised the server.  From there they launched a bunch of attacks against other networks and started spewing out spam.  Our subnet was blackholed by a bunch of networks and our SMTP servers (google) were on the blacklist by several spam houses.</p>
<p>It took us several weeks before we had fully recovered.  It was such a pain in the neck.  From now on we try to rely on others to host our infrastructure.</p>
<p>I&#8217;m happy you hear you climbed back into Google&#8217;s index.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
