<?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"
	>
<channel>
	<title>Comments on: Why My Blog Is Dangerous</title>
	<atom:link href="http://crschmidt.net/blog/312/why-my-blog-is-dangerous/feed/" rel="self" type="application/rss+xml" />
	<link>http://crschmidt.net/blog/312/why-my-blog-is-dangerous/</link>
	<description>Ramblings of a GIS Hacker</description>
	<pubDate>Thu, 04 Dec 2008 00:10:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: handan</title>
		<link>http://crschmidt.net/blog/312/why-my-blog-is-dangerous/#comment-19948</link>
		<dc:creator>handan</dc:creator>
		<pubDate>Tue, 02 Sep 2008 03:01:06 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/?p=312#comment-19948</guid>
		<description>for some rather simple javascript (.js) hacks, and we weren’t defaced or anything like that. Since google began its new security service to alert web surfers of potential security risks many si… The warnings which state something like “This website may be dangerous” on every search</description>
		<content:encoded><![CDATA[<p>for some rather simple javascript (.js) hacks, and we weren’t defaced or anything like that. Since google began its new security service to alert web surfers of potential security risks many si… The warnings which state something like “This website may be dangerous” on every search</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Spacecheck &#187; Blog Archive &#187; Google thinks this site is still dangerous. It isn&#8217;t!</title>
		<link>http://crschmidt.net/blog/312/why-my-blog-is-dangerous/#comment-19934</link>
		<dc:creator>Spacecheck &#187; Blog Archive &#187; Google thinks this site is still dangerous. It isn&#8217;t!</dc:creator>
		<pubDate>Tue, 05 Aug 2008 20:56:43 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/?p=312#comment-19934</guid>
		<description>[...] for some rather simple javascript (.js) hacks, and we weren&#8217;t defaced or anything like that. Since google began its new security service to alert web surfers of potential security risks many si... The warnings which state something like &#8220;This website may be dangerous&#8221; on every search [...]</description>
		<content:encoded><![CDATA[<p>[...] for some rather simple javascript (.js) hacks, and we weren&#8217;t defaced or anything like that. Since google began its new security service to alert web surfers of potential security risks many si&#8230; The warnings which state something like &#8220;This website may be dangerous&#8221; on every search [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dusty Bradshaw</title>
		<link>http://crschmidt.net/blog/312/why-my-blog-is-dangerous/#comment-19933</link>
		<dc:creator>Dusty Bradshaw</dc:creator>
		<pubDate>Tue, 05 Aug 2008 20:40:49 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/?p=312#comment-19933</guid>
		<description>I couldn't agree more. Spacecheck.org must be "dangerous" too, even though we have upgraded to the newest wordpress version and in doing so lost the functionality of the our custom (but not dangerous) comment moderation system, until I re-write it for the new Wordpress...

 Gah.

I have asked google 2 times for manual review and it has been over 24 hours now... nothing. Spacecheck is not dangerous. It isn't like my site is big or anything. It is tiny. It is CLEAN! Be glad at least you got your issues here resolved. Maybe  mine will be resolved in days/weeks?

I even called google and actually spoke to someone on the phone. They  didn't even send a courtesy email sent saying they had found something (.js file) fishy before they lowered the dangerous/malware hammer.

Anyway, this is a good service I guess.. but a speedy clean up of my site (or anyone else's) shouldn't be rewarded with slowness on Google's part to re-index/crawl/vet/checkout/ the sites.</description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t agree more. Spacecheck.org must be &#8220;dangerous&#8221; too, even though we have upgraded to the newest wordpress version and in doing so lost the functionality of the our custom (but not dangerous) comment moderation system, until I re-write it for the new Wordpress&#8230;</p>
<p> Gah.</p>
<p>I have asked google 2 times for manual review and it has been over 24 hours now&#8230; nothing. Spacecheck is not dangerous. It isn&#8217;t like my site is big or anything. It is tiny. It is CLEAN! Be glad at least you got your issues here resolved. Maybe  mine will be resolved in days/weeks?</p>
<p>I even called google and actually spoke to someone on the phone. They  didn&#8217;t even send a courtesy email sent saying they had found something (.js file) fishy before they lowered the dangerous/malware hammer.</p>
<p>Anyway, this is a good service I guess.. but a speedy clean up of my site (or anyone else&#8217;s) shouldn&#8217;t be rewarded with slowness on Google&#8217;s part to re-index/crawl/vet/checkout/ the sites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: itsalljustaride</title>
		<link>http://crschmidt.net/blog/312/why-my-blog-is-dangerous/#comment-19865</link>
		<dc:creator>itsalljustaride</dc:creator>
		<pubDate>Thu, 26 Jun 2008 19:07:17 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/?p=312#comment-19865</guid>
		<description>I just got blacklisted too. In my case I can't seem to log into the Wordpress admin panel since the Firefox 3 "Reported Attack Site" alert keeps borking the login. Had to log in with Safari to even attempt to find the parts I need to fix. Very annoying.</description>
		<content:encoded><![CDATA[<p>I just got blacklisted too. In my case I can&#8217;t seem to log into the Wordpress admin panel since the Firefox 3 &#8220;Reported Attack Site&#8221; alert keeps borking the login. Had to log in with Safari to even attempt to find the parts I need to fix. Very annoying.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill McGonigle</title>
		<link>http://crschmidt.net/blog/312/why-my-blog-is-dangerous/#comment-19665</link>
		<dc:creator>Bill McGonigle</dc:creator>
		<pubDate>Mon, 21 Apr 2008 18:41:53 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/?p=312#comment-19665</guid>
		<description>Hi, Chris - no warning from FF3 (trunk) today.  Looks like you're off the list.  Thanks for posting this - definitely a bit obtuse.</description>
		<content:encoded><![CDATA[<p>Hi, Chris - no warning from FF3 (trunk) today.  Looks like you&#8217;re off the list.  Thanks for posting this - definitely a bit obtuse.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: crschmidt</title>
		<link>http://crschmidt.net/blog/312/why-my-blog-is-dangerous/#comment-19662</link>
		<dc:creator>crschmidt</dc:creator>
		<pubDate>Sun, 20 Apr 2008 00:47:24 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/?p=312#comment-19662</guid>
		<description>JohnMu:

Ah. Okay. That definitely was *not* clear from the UI: I understand the problem, and see why it could happen. 

I do think it's probably not an uncommon thing for a sub-'site' of a website to be infected, given the number of sites that use a separate blogging software (within the same domain) for their website.

Your instructions did help me get to the point where I've requested a review: Here's hoping there's nothing funky that I've missed in my review. Thanks!</description>
		<content:encoded><![CDATA[<p>JohnMu:</p>
<p>Ah. Okay. That definitely was *not* clear from the UI: I understand the problem, and see why it could happen. </p>
<p>I do think it&#8217;s probably not an uncommon thing for a sub-&#8217;site&#8217; of a website to be infected, given the number of sites that use a separate blogging software (within the same domain) for their website.</p>
<p>Your instructions did help me get to the point where I&#8217;ve requested a review: Here&#8217;s hoping there&#8217;s nothing funky that I&#8217;ve missed in my review. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JohnMu</title>
		<link>http://crschmidt.net/blog/312/why-my-blog-is-dangerous/#comment-19661</link>
		<dc:creator>JohnMu</dc:creator>
		<pubDate>Sat, 19 Apr 2008 23:51:52 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/?p=312#comment-19661</guid>
		<description>Hi crschmidt, I think I was a bit confusing in my posting :-). What you need to do is make sure that you have verified ownership of http://crschmidt.net/blog/ (not just crschmidt.net) in your Webmaster Tools account. Once that is done, you should be able to see the warning and the link for the review process. 

In general, when a site gets hacked the whole site gets hacked and has that link right in the root for the whole domain. However, in your case it's only the subdirectory and lower that was hacked and which has the malware warnings. That's why you explicitly need to verify ownership of the subdirectory so that you have access to the warnings and can file a for a review.</description>
		<content:encoded><![CDATA[<p>Hi crschmidt, I think I was a bit confusing in my posting :-). What you need to do is make sure that you have verified ownership of <a href="http://crschmidt.net/blog/" rel="nofollow">http://crschmidt.net/blog/</a> (not just crschmidt.net) in your Webmaster Tools account. Once that is done, you should be able to see the warning and the link for the review process. </p>
<p>In general, when a site gets hacked the whole site gets hacked and has that link right in the root for the whole domain. However, in your case it&#8217;s only the subdirectory and lower that was hacked and which has the malware warnings. That&#8217;s why you explicitly need to verify ownership of the subdirectory so that you have access to the warnings and can file a for a review.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: crschmidt</title>
		<link>http://crschmidt.net/blog/312/why-my-blog-is-dangerous/#comment-19660</link>
		<dc:creator>crschmidt</dc:creator>
		<pubDate>Sat, 19 Apr 2008 23:39:32 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/?p=312#comment-19660</guid>
		<description>JohnMu:

I didn't verify that part of my site didn't have mal-ware: StopBadware/Google only ever detected crschmidt.net/blog/ as being an issue. When I said "verified", I meant that I verified to Google that I was an owner of crschmidt.net, so that I could have full access to the Webmaster Tools.

I still don't see any tool in Webmaster Tools that has any documentation about how to get crschmidt.net/blog/ removed from the Malware list. I did eventually find a 'request reconsideration' link -- it's on the main frontpage for webmaster tools, instead of in the domain specific view where I had been looking -- but it appears to be related to SEO rankings, and claims to take several weeks for processing, so although I have submitted through that mechanism, I don't think that I feel that's actually the one I need to worry about.</description>
		<content:encoded><![CDATA[<p>JohnMu:</p>
<p>I didn&#8217;t verify that part of my site didn&#8217;t have mal-ware: StopBadware/Google only ever detected crschmidt.net/blog/ as being an issue. When I said &#8220;verified&#8221;, I meant that I verified to Google that I was an owner of crschmidt.net, so that I could have full access to the Webmaster Tools.</p>
<p>I still don&#8217;t see any tool in Webmaster Tools that has any documentation about how to get crschmidt.net/blog/ removed from the Malware list. I did eventually find a &#8216;request reconsideration&#8217; link &#8212; it&#8217;s on the main frontpage for webmaster tools, instead of in the domain specific view where I had been looking &#8212; but it appears to be related to SEO rankings, and claims to take several weeks for processing, so although I have submitted through that mechanism, I don&#8217;t think that I feel that&#8217;s actually the one I need to worry about.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JohnMu</title>
		<link>http://crschmidt.net/blog/312/why-my-blog-is-dangerous/#comment-19659</link>
		<dc:creator>JohnMu</dc:creator>
		<pubDate>Sat, 19 Apr 2008 22:49:59 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/?p=312#comment-19659</guid>
		<description>Hey crschmidt, you might want to try to verify just the sub-part of your site that was detected as having malware, If I do a [site:crschmidt.net] query, I see that everything outside of /blog/ is not marked as having malware. If you've already verified http://crschmidt.net/ , you should be able to verify http://crschmidt.net/blog/ without doing anything new.</description>
		<content:encoded><![CDATA[<p>Hey crschmidt, you might want to try to verify just the sub-part of your site that was detected as having malware, If I do a [site:crschmidt.net] query, I see that everything outside of /blog/ is not marked as having malware. If you&#8217;ve already verified <a href="http://crschmidt.net/" rel="nofollow">http://crschmidt.net/</a> , you should be able to verify <a href="http://crschmidt.net/blog/" rel="nofollow">http://crschmidt.net/blog/</a> without doing anything new.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cmn</title>
		<link>http://crschmidt.net/blog/312/why-my-blog-is-dangerous/#comment-19658</link>
		<dc:creator>cmn</dc:creator>
		<pubDate>Sat, 19 Apr 2008 20:53:27 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/?p=312#comment-19658</guid>
		<description>It's not just Google either.

Firefox 3.0b5:

"Reported Attack Site!        

This web site at crschmidt.net has been reported as an attack site and has been blocked based on your security preferences.

Attack sites try to install programs that steal private information, use your computer to attack others, or damage your system.

Some attack sites intentionally distribute harmful software, but many are compromised without the knowledge or permission of their owners."

FF3 uses StopBadware as well IIRC, so it looks like the blame lies with them...</description>
		<content:encoded><![CDATA[<p>It&#8217;s not just Google either.</p>
<p>Firefox 3.0b5:</p>
<p>&#8220;Reported Attack Site!        </p>
<p>This web site at crschmidt.net has been reported as an attack site and has been blocked based on your security preferences.</p>
<p>Attack sites try to install programs that steal private information, use your computer to attack others, or damage your system.</p>
<p>Some attack sites intentionally distribute harmful software, but many are compromised without the knowledge or permission of their owners.&#8221;</p>
<p>FF3 uses StopBadware as well IIRC, so it looks like the blame lies with them&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
