<?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: Virus warning</title>
	<atom:link href="http://www.francesbula.com/uncategorized/virus-warning/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.francesbula.com/uncategorized/virus-warning/</link>
	<description>Vancouver city life and politics</description>
	<lastBuildDate>Tue, 07 Feb 2012 05:41:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Michael Watkins</title>
		<link>http://www.francesbula.com/uncategorized/virus-warning/comment-page-1/#comment-1218</link>
		<dc:creator>Michael Watkins</dc:creator>
		<pubDate>Sun, 09 Nov 2008 07:26:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.francesbula.com/?p=578#comment-1218</guid>
		<description>A quick evaluation of your issue would seem to point not to links from Google but links from anywhere. That in turn means there is something  intercepting http requests at your web host&#039;s level; any link to your site adds a bit of &quot;referrer&quot; data and it seems that the attacking code is using this to trigger it to action.

After an all-too brief look on the internet there does seem to be something of a track record of hacks into your web host and some of its subsidiaries, in particular their control panel code. These shared web hosts run a fairly sophisticated piece of code that manages many dozens, often hundreds or even thousands of sites per server. One compromise generally means many more. Given that many hours have gone by and your site still suffers from the cross site linking attack, you should consider whether your hosting firm is up to the task. If a host is that inept, they are not worth sticking with.

Get a local backup of your *data* - an export from your blogging system; a mirror copy of your blog as is, as a static site if nothing else in case the worst happens. Do this as soon as possible just in case your hosting company does something radical and stupid like erasing/formatting their disk drives and starting over. 

Don&#039;t laugh, I&#039;ve seen bad web hosts do all that and worse.</description>
		<content:encoded><![CDATA[<p>A quick evaluation of your issue would seem to point not to links from Google but links from anywhere. That in turn means there is something  intercepting http requests at your web host&#8217;s level; any link to your site adds a bit of &#8220;referrer&#8221; data and it seems that the attacking code is using this to trigger it to action.</p>
<p>After an all-too brief look on the internet there does seem to be something of a track record of hacks into your web host and some of its subsidiaries, in particular their control panel code. These shared web hosts run a fairly sophisticated piece of code that manages many dozens, often hundreds or even thousands of sites per server. One compromise generally means many more. Given that many hours have gone by and your site still suffers from the cross site linking attack, you should consider whether your hosting firm is up to the task. If a host is that inept, they are not worth sticking with.</p>
<p>Get a local backup of your *data* &#8211; an export from your blogging system; a mirror copy of your blog as is, as a static site if nothing else in case the worst happens. Do this as soon as possible just in case your hosting company does something radical and stupid like erasing/formatting their disk drives and starting over. </p>
<p>Don&#8217;t laugh, I&#8217;ve seen bad web hosts do all that and worse.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

