<?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: EXPLAINING TEMPORARY CLOSING DOWN OF SITE</title>
	<atom:link href="http://www.pocket-bike-racing.com.au/blog/2009/11/explaining-temporary-closing-down-of-site/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pocket-bike-racing.com.au/blog/2009/11/explaining-temporary-closing-down-of-site/</link>
	<description></description>
	<lastBuildDate>Tue, 15 Dec 2009 03:10:58 +1100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: chris</title>
		<link>http://www.pocket-bike-racing.com.au/blog/2009/11/explaining-temporary-closing-down-of-site/comment-page-1/#comment-158</link>
		<dc:creator>chris</dc:creator>
		<pubDate>Tue, 15 Dec 2009 03:10:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.pocket-bike-racing.com.au/blog/?p=70#comment-158</guid>
		<description>Hi Gary

Of course I remember you - our former chief mod! 

PBR tech help appreciates your comments but they say that this was not the cause of the problem. 

We think we have identified the cause and they are working at taking measures now to stop it happening again. 

We are really sorry that the second time the site went down was for such a long time. It was totally outside of our control.

We have now moved the site to a new server where a forced closure can not happen again.

This is life on the Internet and no one is spared from the risk of fraud, hacking and phishing. 

Cheers.........PBR Admin</description>
		<content:encoded><![CDATA[<p>Hi Gary</p>
<p>Of course I remember you &#8211; our former chief mod! </p>
<p>PBR tech help appreciates your comments but they say that this was not the cause of the problem. </p>
<p>We think we have identified the cause and they are working at taking measures now to stop it happening again. </p>
<p>We are really sorry that the second time the site went down was for such a long time. It was totally outside of our control.</p>
<p>We have now moved the site to a new server where a forced closure can not happen again.</p>
<p>This is life on the Internet and no one is spared from the risk of fraud, hacking and phishing. </p>
<p>Cheers&#8230;&#8230;&#8230;PBR Admin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary Hope</title>
		<link>http://www.pocket-bike-racing.com.au/blog/2009/11/explaining-temporary-closing-down-of-site/comment-page-1/#comment-156</link>
		<dc:creator>Gary Hope</dc:creator>
		<pubDate>Mon, 14 Dec 2009 05:15:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.pocket-bike-racing.com.au/blog/?p=70#comment-156</guid>
		<description>Hi Chris. 

I hope you remember who I am.
I doubt the problem was caused by what you&#039;ve mentioned in the above blog post. PBR was one of many sites that were taken down recently due to the same issues. Overclockers Australia, Whirlpool, JB Hifi just to name a few all suffered the same fate due to what if I recall correctly was a SQL security hole.

Overclocksers Australi was briefly redirecting a totally different site that was used to screw up users systems and the database was compromised.
I&#039;d advise that you put out a security alert to all users to change their user account passwords incase they were compromised as well. Many users use the same passwords for many sites so those accounts will be vulrunable as well.

Kind Regards
Gary Hope</description>
		<content:encoded><![CDATA[<p>Hi Chris. </p>
<p>I hope you remember who I am.<br />
I doubt the problem was caused by what you&#8217;ve mentioned in the above blog post. PBR was one of many sites that were taken down recently due to the same issues. Overclockers Australia, Whirlpool, JB Hifi just to name a few all suffered the same fate due to what if I recall correctly was a SQL security hole.</p>
<p>Overclocksers Australi was briefly redirecting a totally different site that was used to screw up users systems and the database was compromised.<br />
I&#8217;d advise that you put out a security alert to all users to change their user account passwords incase they were compromised as well. Many users use the same passwords for many sites so those accounts will be vulrunable as well.</p>
<p>Kind Regards<br />
Gary Hope</p>
]]></content:encoded>
	</item>
</channel>
</rss>

