<?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>tmllr &#187; password</title>
	<atom:link href="http://www.tmllr.com/tag/password/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tmllr.com</link>
	<description>Building. Tracking. Optimizing. Inspiring.</description>
	<lastBuildDate>Wed, 19 Oct 2011 18:01:31 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Happiness is a Strong Password</title>
		<link>http://www.tmllr.com/2009/01/happiness-is-a-strong-password/</link>
		<comments>http://www.tmllr.com/2009/01/happiness-is-a-strong-password/#comments</comments>
		<pubDate>Thu, 08 Jan 2009 05:44:21 +0000</pubDate>
		<dc:creator>Tom Miller</dc:creator>
				<category><![CDATA[Cool Tools]]></category>
		<category><![CDATA[Social Media]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[password]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://www.tomsanalytics.com/?p=34</guid>
		<description><![CDATA[Twitter was hacked this past weekend, and it was a simple as going to http://www.twitter.com/admin/ with the username of &#8220;admin&#8221; and the password of &#8220;Happiness&#8221;. &#8220;Happiness&#8221;? Are you kidding me? Twitter&#8217;s back-end system allowed an unlimited number of attempts and also allowed such a weak password, so Twitter&#8217;s development team is partially to blame. A [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.wired.com/27bstroke6/2009/01/professed-twitt.html" target="_new">Twitter was hacked this past weekend</a>, and it was a simple as going to http://www.twitter.com/admin/ with the username of &#8220;admin&#8221; and the password of &#8220;Happiness&#8221;.  &#8220;Happiness&#8221;?  Are you kidding me?</p>
<p>Twitter&#8217;s back-end system allowed an unlimited number of attempts and also allowed such a weak password, so Twitter&#8217;s development team is partially to blame.</p>
<p>A share of the blame should also go to Twitter&#8217;s web analysts.  Much like you should set up some type of custom reporting based on server error messages (404&#8242;s and 500&#8242;s), setting up an alert system and analytics on administrative systems, particularly when it comes to  access to those systems, should be a priority for the launch of any site.</p>
<p>However, the majority of the blame should be paced at the feet of the administrator.  Whoever did this is not alone.  A number of years ago I was involved in a site security audit where we essentially ran the following SQL statement (it wasn&#8217;t this simple, but you get the idea):</p>
<blockquote><p>select password, count(password)<br />
from users<br />
group by password<br />
order by count(password) DESC</p></blockquote>
<p>The results of this on the site (and, I imagine every site) were shocking.  The top positions were held down by passwords such as &#8220;password&#8221;, &#8220;12345&#8243;, and the names of cartoon characters.</p>
<p>Factoring in proper nouns, capitalization differences, and prefixes and suffixes, there are only a couple of hundred million passwords that are based on the English language.  If the hackers were able to brute-force attack the form at the rate of 10 tries per second, they could exhaust every iteration of every word in English in a month.</p>
<p>If you look at using random letters, numbers, and symbols in a password, the possibilities balloon.  A six-character password of this type has over 200 BILLION combinations.  At the same rate, it would take a brute-force attack over TEN YEARS to exhaust the possibilities.  An eight-character password would take over fifty thousand years!  So you can see the power of strong passwords.</p>
<p>To avoid a screw-up of such magnitude with your personal and professional applications, try the following two sites to generate strong passwords (and avoid ones that are actual words):</p>
<p><a href="https://secure.msdservices.com/apg/" target="_new">Automated Password Generator Online</a>:  This allows you to set criteria for your potential passwords such as length and character set.</p>
<p><a href="https://www.grc.com/passwords.htm" target="_new">GRC&#8217;s Ultra High Security Password Generator</a>:  This site generates three types of <em>truly</em> random strings with each page refresh.  It also goes into the math of 512-bit encryption.</p>
<p>Good luck and stay safe!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.tmllr.com/2009/01/happiness-is-a-strong-password/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

