<?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>Kommentarer til: How to not tell about a security breach?</title>
	<atom:link href="http://hovenko.no/blog/2009/09/07/how-to-not-tell-about-a-security-breach/feed/" rel="self" type="application/rss+xml" />
	<link>https://hovenko.no/blog/2009/09/07/how-to-not-tell-about-a-security-breach/</link>
	<description>En blogg av Knut-Olav</description>
	<lastBuildDate>Thu, 02 Sep 2021 20:06:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Knut-Olav</title>
		<link>https://hovenko.no/blog/2009/09/07/how-to-not-tell-about-a-security-breach/comment-page-1/#comment-8329</link>
		<dc:creator>Knut-Olav</dc:creator>
		<pubDate>Tue, 08 Sep 2009 17:52:49 +0000</pubDate>
		<guid isPermaLink="false">http://hovenko.no/blog/?p=346#comment-8329</guid>
		<description>Ok, so I finally got to the point of upgrading to WordPress 2.8.4. Since I use Subversion to organize my blog source code I can easily get the diff between WordPress version 2.8.3 and 2.8.4. There is nothing in that diff that bings any security to my blog.

Sure, if a spam bot creates millions of user accounts on my using different email addresses they might brute force the activation key in a few tries. Looking from another perspective millions of bots might try to brute force the activation key of my admin account. But after I apply this patch, they still can! If your admin account is named &quot;admin&quot; of course.

The only benefit from a security perspective of upgrading from 2.8.3 to 2.8.4 is when your admin account is not named admin. Then the bots have to guess the username too.

In the short. Rename your admin account!</description>
		<content:encoded><![CDATA[<p>Ok, so I finally got to the point of upgrading to WordPress 2.8.4. Since I use Subversion to organize my blog source code I can easily get the diff between WordPress version 2.8.3 and 2.8.4. There is nothing in that diff that bings any security to my blog.</p>
<p>Sure, if a spam bot creates millions of user accounts on my using different email addresses they might brute force the activation key in a few tries. Looking from another perspective millions of bots might try to brute force the activation key of my admin account. But after I apply this patch, they still can! If your admin account is named &#8220;admin&#8221; of course.</p>
<p>The only benefit from a security perspective of upgrading from 2.8.3 to 2.8.4 is when your admin account is not named admin. Then the bots have to guess the username too.</p>
<p>In the short. Rename your admin account!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
