<?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>Network Lighthouse&#187; Security</title>
	<atom:link href="http://www.networklighthouse.com/category/security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.networklighthouse.com</link>
	<description>Shining the Light on Security and Privacy</description>
	<lastBuildDate>Sat, 10 Jul 2010 08:02:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Palin e-mail hacker found guilty</title>
		<link>http://www.networklighthouse.com/2010/05/palin-e-mail-hacker-found-guilty/</link>
		<comments>http://www.networklighthouse.com/2010/05/palin-e-mail-hacker-found-guilty/#comments</comments>
		<pubDate>Mon, 03 May 2010 12:16:17 +0000</pubDate>
		<dc:creator>Daniel</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[passwords]]></category>

		<guid isPermaLink="false">http://www.networklighthouse.com/?p=244</guid>
		<description><![CDATA[&#8212; From the article The college student accused of hacking into Sarah Palin&#8217;s e-mail account in 2008 has been found guilty of obstruction of justice and unauthorized access of a computer. The verdict against 22-year-old David Kernell came down late Friday, with sentencing to follow later. &#8212; via Palin e-mail hacker found guilty. I have [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.networklighthouse.com%2F2010%2F05%2Fpalin-e-mail-hacker-found-guilty%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.networklighthouse.com%2F2010%2F05%2Fpalin-e-mail-hacker-found-guilty%2F&amp;source=Daniel_Thomas&amp;style=normal&amp;service=cli.gs&amp;service_api=b23fe3c963328d1c08788b47b9493918" height="61" width="50" /><br />
			</a>
		</div>
<p>&#8212; From the article</p>
<p>The college student accused of hacking into Sarah Palin&#8217;s e-mail account  in 2008 has been found guilty of obstruction of justice and  unauthorized access of a computer. The verdict against 22-year-old David  Kernell came down late Friday, with sentencing to follow later.</p>
<p>&#8212; via <a href="http://arstechnica.com/tech-policy/news/2010/04/palin-e-mail-hacker-found-guilty.ars?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=rss">Palin e-mail hacker found guilty</a>.</p>
<p>I have mixed feelings about this outcome, while the individual undoubtadly did the wrong thing be breaking into someones email account, he also highlighted the risks we all face(particularly public figures) as a result of the (secret) question/answer system for reseting forgotten passwords.</p>
<p>I don&#8217;t think these issues could have been highlighted in any more clear way to raise the publics awareness of this.  No matter how many times the security iductry warns against the weaknesses of the present system, it takes real incidents (like the above) before the issues are generally accepted.</p>
<p>-Daniel</p>
]]></content:encoded>
			<wfw:commentRss>http://www.networklighthouse.com/2010/05/palin-e-mail-hacker-found-guilty/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Interesting Spam</title>
		<link>http://www.networklighthouse.com/2010/03/interesting-spam/</link>
		<comments>http://www.networklighthouse.com/2010/03/interesting-spam/#comments</comments>
		<pubDate>Sun, 07 Mar 2010 11:19:01 +0000</pubDate>
		<dc:creator>Daniel</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[spam]]></category>

		<guid isPermaLink="false">http://www.networklighthouse.com/?p=221</guid>
		<description><![CDATA[A couple of days ago I got a comment on one of my posts that struck me as unusual, it was marked as spam (thanks to akismet), but didn&#8217;t read like your standard spam. Here&#8217;s the text: Good points raised here, (well, what I could read of it). I am afflicted with color blindness (tritanopia [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.networklighthouse.com%2F2010%2F03%2Finteresting-spam%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.networklighthouse.com%2F2010%2F03%2Finteresting-spam%2F&amp;source=Daniel_Thomas&amp;style=normal&amp;service=cli.gs&amp;service_api=b23fe3c963328d1c08788b47b9493918" height="61" width="50" /><br />
			</a>
		</div>
<p>A couple of days ago I got a comment on one of my posts that struck me as unusual, it was marked as spam (thanks to akismet), but didn&#8217;t read like your standard spam. Here&#8217;s the text:</p>
<p style="text-align: justify; padding-left: 30px;">Good points raised here, (well, what I could read of it). I am afflicted with color blindness (tritanopia to be exact). I use Chrome browser (unsure if that matters), and a lot of your site is a little difficult for me to read. I don’t wish to whinge, and I know it is my problem really, nonetheless it would be cool if you could bear in mind color blind visitors when carrying out the next site re-working.</p>
<p>After a first glance I almost approved it without further thought, however something struck me as odd.   The comment linked to p_l_a_y_n_i_c_e .c_o .u_k, which backs up the post, still not convinced I did some googling and found a number of blogs with almost identically worded comments.   There was some differences in the wording, the browser changes, I&#8217;ve seen Chrome, Konqurer and Safari and there are a couple of different introductions.</p>
<p>The only thing I am sure of now is that this isn&#8217;t a legitimate comment, but is meant to serve some other purpose.   It may be just for self promotion, grandfathering links for search eangines, or potentially preparation for a drive by download attack.  I&#8217;ll keep track of the page and report any changes.</p>
<p>-Daniel</p>
]]></content:encoded>
			<wfw:commentRss>http://www.networklighthouse.com/2010/03/interesting-spam/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Top 10 Worst Data Losses or Breaches</title>
		<link>http://www.networklighthouse.com/2009/12/top-10-worst-data-losses-or-breaches/</link>
		<comments>http://www.networklighthouse.com/2009/12/top-10-worst-data-losses-or-breaches/#comments</comments>
		<pubDate>Tue, 29 Dec 2009 23:28:48 +0000</pubDate>
		<dc:creator>Daniel</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[data breaches]]></category>
		<category><![CDATA[encryption technology]]></category>
		<category><![CDATA[information management]]></category>
		<category><![CDATA[sensitive data]]></category>

		<guid isPermaLink="false">http://www.networklighthouse.com/?p=159</guid>
		<description><![CDATA[It&#8217;s been a while since I&#8217;ve done any writing on InfoSec topics, but it&#8217;s my new years resolution to take it up again, so expect more articles on info sec stuff from now on. DataBreaches.net have updated their list of the top 10 Data breaches of all time.   What I find most disturbing about the [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.networklighthouse.com%2F2009%2F12%2Ftop-10-worst-data-losses-or-breaches%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.networklighthouse.com%2F2009%2F12%2Ftop-10-worst-data-losses-or-breaches%2F&amp;source=Daniel_Thomas&amp;style=normal&amp;service=cli.gs&amp;service_api=b23fe3c963328d1c08788b47b9493918" height="61" width="50" /><br />
			</a>
		</div>
<p>It&#8217;s been a while since I&#8217;ve done any writing on InfoSec topics, but it&#8217;s my new years resolution to take it up again, so expect more articles on info sec stuff from now on.</p>
<p>DataBreaches.net have updated their list of the <a href="http://www.databreaches.net/?p=7691">top 10 Data breaches</a> of all time.   What I find most disturbing about the list, isn&#8217;t the volumes (although that&#8217;s still concerning), is that 4 of the top 10 were due to poor information management and/or lack of encryption.   The causes for the other breaches (such as insiders leaking information) are harder to solve, and as such a little more (not a lot though) understandable.</p>
<ul>
<li>National Archives (70 Million)</li>
<li>Department of Veterans Affairs ( 26 Million)</li>
<li>HMRC (25 Million)</li>
<li>T-Mobile (17 Million)</li>
</ul>
<p>With the exception of Veterans Affairs, all of these have occured in the last 2 years, when the use of disk/tape encryption technology came into the mainstream.  There really is no excuse for these type of breaches anymore, if companies made it standard practice to encrypt sensitive data where ever it lives, then that would mean that over the past 2 years there would have been 128 Million less records breached. That&#8217;s almost as many were revealed in the Heartland hack!</p>
<p>Of course the top 10 doesn&#8217;t include breaches that go unnoticed and unreported, and if you start thinking about that you start to wonder how bad the problem really is.</p>
<p>-Daniel</p>
]]></content:encoded>
			<wfw:commentRss>http://www.networklighthouse.com/2009/12/top-10-worst-data-losses-or-breaches/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What the Web knows about you</title>
		<link>http://www.networklighthouse.com/2009/02/what-the-web-knows-about-you/</link>
		<comments>http://www.networklighthouse.com/2009/02/what-the-web-knows-about-you/#comments</comments>
		<pubDate>Wed, 18 Feb 2009 20:55:30 +0000</pubDate>
		<dc:creator>Daniel</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[identity theft]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[profiling]]></category>

		<guid isPermaLink="false">http://www.networklighthouse.com/?p=71</guid>
		<description><![CDATA[Online privacy and the implications of data aggregation is a bit of a passion of mine, that&#8217;s part of what inspired me to write the thunderbird plugin. Here&#8217;s an interesting story about one journalists discovery of what he found out about himself. What the Web knows about you. People wonder why identity theft happens, so [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.networklighthouse.com%2F2009%2F02%2Fwhat-the-web-knows-about-you%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.networklighthouse.com%2F2009%2F02%2Fwhat-the-web-knows-about-you%2F&amp;source=Daniel_Thomas&amp;style=normal&amp;service=cli.gs&amp;service_api=b23fe3c963328d1c08788b47b9493918" height="61" width="50" /><br />
			</a>
		</div>
<p>Online privacy and the implications of data aggregation is a bit of a passion of mine, that&#8217;s part of what inspired me to write the thunderbird plugin.</p>
<p>Here&#8217;s an interesting story about one journalists discovery of what he found out about himself.</p>
<p><a href="http://www.computerworld.com/action/article.do?command=viewArticleBasic&amp;articleId=9125058">What the Web knows about you</a>.</p>
<p>People wonder why identity theft happens, so much of our personal data is available online these days that it&#8217;s possible to build a fairly complete profile of anyone you want.  Just one of the reasons everyone needs to be careful needs to be careful of what they post on social networking sites.</p>
<p>-Daniel</p>
]]></content:encoded>
			<wfw:commentRss>http://www.networklighthouse.com/2009/02/what-the-web-knows-about-you/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Viruses: Hackers Using Fake Parking Tickets to Infect Computers</title>
		<link>http://www.networklighthouse.com/2009/02/viruses-hackers-using-fake-parking-tickets-to-infect-computers/</link>
		<comments>http://www.networklighthouse.com/2009/02/viruses-hackers-using-fake-parking-tickets-to-infect-computers/#comments</comments>
		<pubDate>Mon, 09 Feb 2009 21:17:03 +0000</pubDate>
		<dc:creator>Daniel</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[scam]]></category>
		<category><![CDATA[trojan]]></category>

		<guid isPermaLink="false">http://www.networklighthouse.com/?p=86</guid>
		<description><![CDATA[Here&#8217;s an interesting twist on an old scam.   In a town in the US someone has been issuing fake parking tickets.   The fake tickets instruct the victim to go to a website to pay their fine, the website in turn says that you have to download a &#8216;toolbar&#8217; to see the details and pay their [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.networklighthouse.com%2F2009%2F02%2Fviruses-hackers-using-fake-parking-tickets-to-infect-computers%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.networklighthouse.com%2F2009%2F02%2Fviruses-hackers-using-fake-parking-tickets-to-infect-computers%2F&amp;source=Daniel_Thomas&amp;style=normal&amp;service=cli.gs&amp;service_api=b23fe3c963328d1c08788b47b9493918" height="61" width="50" /><br />
			</a>
		</div>
<p>Here&#8217;s an interesting twist on an old scam.   In a town in the US someone has been issuing fake parking tickets.   The fake tickets instruct the victim to go to a website to pay their fine, the website in turn says that you have to download a &#8216;toolbar&#8217; to see the details and pay their fine.</p>
<p>Needless to say the toolbar is really a trojan infested piece of malware, which will continue to spawn popups including the notorious Antivirus 2009.</p>
<p><a href="http://i.gizmodo.com/5148817/hackers-using-fake-parking-tickets-to-infect-computers">Viruses: Hackers Using Fake Parking Tickets to Infect Computers</a>.</p>
<p>Yet another example of how the bad guys are changing their tactics to stay ahead of the curve.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.networklighthouse.com/2009/02/viruses-hackers-using-fake-parking-tickets-to-infect-computers/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>What You Really Need To Know About Data Loss Prevention &#8211; insider threats/Management</title>
		<link>http://www.networklighthouse.com/2009/02/what-you-really-need-to-know-about-data-loss-prevention-insider-threatsmanagement/</link>
		<comments>http://www.networklighthouse.com/2009/02/what-you-really-need-to-know-about-data-loss-prevention-insider-threatsmanagement/#comments</comments>
		<pubDate>Sat, 07 Feb 2009 07:39:32 +0000</pubDate>
		<dc:creator>Daniel</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[accidental losses]]></category>
		<category><![CDATA[data loss prevention]]></category>
		<category><![CDATA[information security]]></category>

		<guid isPermaLink="false">http://www.networklighthouse.com/?p=81</guid>
		<description><![CDATA[Data Loss Prevention is one of the hot topics in Information Security at the moment, largely brought about by the numerous accidental losses of sensitive information that have been in the press over the last few years. Here is a decent article that covers what it is and how it works: What You Really Need [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.networklighthouse.com%2F2009%2F02%2Fwhat-you-really-need-to-know-about-data-loss-prevention-insider-threatsmanagement%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.networklighthouse.com%2F2009%2F02%2Fwhat-you-really-need-to-know-about-data-loss-prevention-insider-threatsmanagement%2F&amp;source=Daniel_Thomas&amp;style=normal&amp;service=cli.gs&amp;service_api=b23fe3c963328d1c08788b47b9493918" height="61" width="50" /><br />
			</a>
		</div>
<p>Data Loss Prevention is one of the hot topics in Information Security at the moment, largely brought about by the numerous accidental losses of sensitive information that have been in the press over the last few years.</p>
<p>Here is a decent article that covers what it is and how it works:</p>
<p><a href="http://www.darkreading.com/security/management/showArticle.jhtml?articleID=213300864&amp;cid=RSSfeed">What You Really Need To Know About Data Loss Prevention &#8211; insider threats/Management &#8211; DarkReading</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.networklighthouse.com/2009/02/what-you-really-need-to-know-about-data-loss-prevention-insider-threatsmanagement/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Who&#8217;s walking out with your secrets</title>
		<link>http://www.networklighthouse.com/2009/02/whos-walking-out-with-your-secrets/</link>
		<comments>http://www.networklighthouse.com/2009/02/whos-walking-out-with-your-secrets/#comments</comments>
		<pubDate>Sun, 01 Feb 2009 07:56:45 +0000</pubDate>
		<dc:creator>Daniel</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[insider]]></category>
		<category><![CDATA[physical security]]></category>
		<category><![CDATA[theft]]></category>

		<guid isPermaLink="false">http://www.networklighthouse.com/?p=69</guid>
		<description><![CDATA[While this is not my usual topic, there&#8217;s something very wrong with this story, it pays to remember how closely information security is tied to physical security: Former Energy Worker Admits Trying To Sell Nuclear Secrets &#8211; Insider threats/Attacks &#8211; DarkReading. The short of it is that a janitor managed to walk out of a [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.networklighthouse.com%2F2009%2F02%2Fwhos-walking-out-with-your-secrets%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.networklighthouse.com%2F2009%2F02%2Fwhos-walking-out-with-your-secrets%2F&amp;source=Daniel_Thomas&amp;style=normal&amp;service=cli.gs&amp;service_api=b23fe3c963328d1c08788b47b9493918" height="61" width="50" /><br />
			</a>
		</div>
<p>While this is not my usual topic, there&#8217;s something very wrong with this story, it pays to remember how closely information security is tied to physical security:</p>
<p><a href="http://www.darkreading.com/security/attacks/showArticle.jhtml?articleID=212902962&amp;cid=RSSfeed">Former Energy Worker Admits Trying To Sell Nuclear Secrets &#8211; Insider threats/Attacks &#8211; DarkReading</a>.</p>
<p>The short of it is that a janitor managed to walk out of a US DoD site with a number of components developed as part of a nuclear research project.   After successfully getting them on site, he tried selling them to the French Government.  Fortunately it was the French, not some semi-hostile government, and so they reported him to the FBI who arrested him.</p>
<p>What can we learn from this story?  Firstly treat your cleaners as if they are privy to your most sensitive secrets, because in all likelihood they are. Things get left on desks, in photocopiers, &#8216;secure&#8217; document disposal bins  all the time, and cleaners often have unsupervised access to all parts of your offices.</p>
<p>Secondly, a number of vital security controls were either missing or failed for him to take them.  Inventory control should have noticed that sensitive items were missing,and so sparked a full scale investigation.  Secondly it shows the weakness  of manual security searches, why was he taking equipment on and offsite anyway.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.networklighthouse.com/2009/02/whos-walking-out-with-your-secrets/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Payment Processor Breach May Be Largest Ever</title>
		<link>http://www.networklighthouse.com/2009/01/payment-processor-breach-may-be-largest-ever/</link>
		<comments>http://www.networklighthouse.com/2009/01/payment-processor-breach-may-be-largest-ever/#comments</comments>
		<pubDate>Sun, 25 Jan 2009 00:09:37 +0000</pubDate>
		<dc:creator>Daniel</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[breach]]></category>
		<category><![CDATA[credit cards numbers]]></category>
		<category><![CDATA[cyber criminals]]></category>
		<category><![CDATA[pci dss]]></category>

		<guid isPermaLink="false">http://www.networklighthouse.com/?p=63</guid>
		<description><![CDATA[Somewhere in the region of 100 million credit cards numbers have been acquired from payment processor Heartland by cyber-criminals in what is likey to be the largest breach of its kind to date. Payment Processor Breach May Be Largest Ever &#8211; Security Fix. What makes this worse is that Heartland was PCI DSS compliant, having [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.networklighthouse.com%2F2009%2F01%2Fpayment-processor-breach-may-be-largest-ever%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.networklighthouse.com%2F2009%2F01%2Fpayment-processor-breach-may-be-largest-ever%2F&amp;source=Daniel_Thomas&amp;style=normal&amp;service=cli.gs&amp;service_api=b23fe3c963328d1c08788b47b9493918" height="61" width="50" /><br />
			</a>
		</div>
<p>Somewhere in the region of 100 million credit cards numbers have been acquired from payment processor Heartland by cyber-criminals in what is likey to be the largest breach of its kind to date.</p>
<p><a href="http://voices.washingtonpost.com/securityfix/2009/01/payment_processor_breach_may_b.html">Payment Processor Breach May Be Largest Ever &#8211; Security Fix</a>.</p>
<p>What makes this worse is that Heartland was PCI DSS compliant, having passed the audit April 2008.    Undoubtedly this will bring about even further debate about the validity of the PCI standard.</p>
<p>-Daniel</p>
]]></content:encoded>
			<wfw:commentRss>http://www.networklighthouse.com/2009/01/payment-processor-breach-may-be-largest-ever/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Forging SSL Certificates</title>
		<link>http://www.networklighthouse.com/2009/01/forging-ssl-certificates/</link>
		<comments>http://www.networklighthouse.com/2009/01/forging-ssl-certificates/#comments</comments>
		<pubDate>Thu, 01 Jan 2009 00:07:36 +0000</pubDate>
		<dc:creator>Daniel</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[certificate authority]]></category>
		<category><![CDATA[md5]]></category>
		<category><![CDATA[ssl certificates]]></category>
		<category><![CDATA[vulnerability]]></category>

		<guid isPermaLink="false">http://www.networklighthouse.com/2009/01/forging-ssl-certificates/</guid>
		<description><![CDATA[For a while now, it&#8217;s been known that the md5 hashing algorithm is susceptible to collisions, reducing the level of security it provides, although predominately in only a theoretical manner. Now some enterprising researchers have used this vulnerability (along with 200 ps3&#8242;s) to create a fake certificate authority, ensentially allowing them to create certificates for [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.networklighthouse.com%2F2009%2F01%2Fforging-ssl-certificates%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.networklighthouse.com%2F2009%2F01%2Fforging-ssl-certificates%2F&amp;source=Daniel_Thomas&amp;style=normal&amp;service=cli.gs&amp;service_api=b23fe3c963328d1c08788b47b9493918" height="61" width="50" /><br />
			</a>
		</div>
<p>For a while now, it&#8217;s been known that the md5 hashing algorithm is susceptible to collisions, reducing the level of security it provides, although predominately in only a theoretical manner.</p>
<p>Now some enterprising researchers have used this vulnerability (along with 200 ps3&#8242;s) to create a fake certificate authority, ensentially allowing them to create certificates for any name that browsers will trust implicitly.</p>
<p><a href="http://www.schneier.com/blog/archives/2008/12/forging_ssl_cer.html">Schneier on Security: Forging SSL Certificates</a>.</p>
<p>There are a couple of factors that mean the internet isn&#8217;t &#8216;broken&#8217; by this:</p>
<ul>
<li>By itself it&#8217;s not particularly useful to have a certificate for &#8220;example.com&#8221;, I also need to convince someone that &#8220;example.com&#8221; is at my ip address. (Some of the recent dns vulnerabilities could be used for this)</li>
<li>Most CA&#8217;s don&#8217;t use MD5 anymore, those that do are moving to more secure algorithms.</li>
</ul>
<p>One comment that Bruce made in his blog (linked above) that I disagree with is about people ignoring SSL warning messages, I have never (and make sure my family and colleagues do the same) ignored SSL warnings,  they are there for a reason and I make sure if I see one I understand why I am seeing it before doing anything I wouldn&#8217;t want to be compromised.  I strongly recommend that SSL warnings (like all security messages) seriously.</p>
<p>-Daniel</p>
]]></content:encoded>
			<wfw:commentRss>http://www.networklighthouse.com/2009/01/forging-ssl-certificates/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Relative Password Strength</title>
		<link>http://www.networklighthouse.com/2008/12/relative-password-strength/</link>
		<comments>http://www.networklighthouse.com/2008/12/relative-password-strength/#comments</comments>
		<pubDate>Mon, 01 Dec 2008 22:12:01 +0000</pubDate>
		<dc:creator>Daniel</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[password complexity]]></category>
		<category><![CDATA[password recovery]]></category>
		<category><![CDATA[password strength]]></category>
		<category><![CDATA[passwords]]></category>

		<guid isPermaLink="false">http://www.networklighthouse.com/?p=42</guid>
		<description><![CDATA[e are always told to choose strong passwords, over eight characters, with lower &#38; upper case letter, numbers and symbols, but really what difference does it make. Lets have a look at 4 different classes of passwords each 8 characters: A) Lower case letters only B) Mixed case letters C) Mixed case letters and digits [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.networklighthouse.com%2F2008%2F12%2Frelative-password-strength%2F"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.networklighthouse.com%2F2008%2F12%2Frelative-password-strength%2F&amp;source=Daniel_Thomas&amp;style=normal&amp;service=cli.gs&amp;service_api=b23fe3c963328d1c08788b47b9493918" height="61" width="50" /><br />
			</a>
		</div>
<p>e are always told to choose strong passwords, over eight characters, with lower &amp; upper case letter, numbers and symbols, but really what difference does it make.</p>
<p>Lets have a look at 4 different classes of passwords each 8 characters:</p>
<p>A) Lower case letters only</p>
<p>B) Mixed case letters</p>
<p>C) Mixed case letters and digits</p>
<p>D) Mixed case letters, digits and 32 symbols</p>
<p>The table below shows the number of possible combinations and the time to crack based on <a href="http://www.elcomsoft.com/edpr.html" target="_blank">Elcomsoft</a>&#8216;s rates for md5 password recovery on a dual core processor (4.7 million passwords/second)</p>
<table style="border-collapse: collapse; width: 256pt; text-align: center;" border="1" cellspacing="0" cellpadding="0" width="341">
<col style="width: 48pt;" width="64"></col>
<col style="width: 138pt;" width="184"></col>
<col style="width: 70pt;" width="93"></col>
<tbody>
<tr style="height: 15pt;" height="20">
<td class="xl66" style="height: 15pt; width: 48pt;" width="64" height="20">Class</td>
<td class="xl67" style="width: 138pt;" width="184">Combinations</td>
<td class="xl66" style="width: 70pt;" width="93">Time to Crack</td>
</tr>
<tr style="height: 15pt;" height="20">
<td class="xl66" style="height: 15pt;" height="20">A</td>
<td class="xl65"><span> </span>208,827,064,576</td>
<td class="xl67">44 seconds</td>
</tr>
<tr style="height: 15pt;" height="20">
<td class="xl66" style="height: 15pt;" height="20">B</td>
<td class="xl65"><span> </span>53,459,728,531,456</td>
<td class="xl67">3 hours</td>
</tr>
<tr style="height: 15pt;" height="20">
<td class="xl66" style="height: 15pt;" height="20">C</td>
<td class="xl65"><span> </span>218,340,105,584,896</td>
<td class="xl67">12 hours</td>
</tr>
<tr style="height: 15pt;" height="20">
<td class="xl66" style="height: 15pt; text-align: center;" height="20">D</td>
<td class="xl65"><span> </span>6,095,689,385,410,820</td>
<td class="xl67">15 days</td>
</tr>
</tbody>
</table>
<p>So you can see a password that just has lower case letters can be cracked in less than a minute!  While a password that covers the full spectrum of character types will take 15 days, that&#8217;s a lot of extra effort to get into your account.</p>
<p>So what if you want to have a strong password, but you don&#8217;t want to have to remember a string with upper case letters, numbers and symbols.  Can you have a password, containing just lower case letters, that provides as much protection as a password that contains at least 1 character from each group?  Absolutely, you just have to trade complexity for length.  Have a look at this table to see how long passwords need to be to be at least as strong as a 8 character class D password.</p>
<table style="border-collapse: collapse; text-align: center; height: 101px;" border="1" cellspacing="0" cellpadding="0" width="193">
<col style="width: 48pt;" width="64"></col>
<col style="width: 138pt;" width="184"></col>
<tbody>
<tr style="height: 15pt;" height="20">
<td class="xl65" style="height: 15pt; width: 48pt;" width="64" height="20">Class</td>
<td class="xl65" style="border-left: medium none; width: 138pt;" width="184">Number of   Characters</td>
</tr>
<tr style="height: 15pt;" height="20">
<td class="xl65" style="border-top: medium none; height: 15pt;" height="20">A</td>
<td class="xl66" style="border-top: medium none; border-left: medium none;">12</td>
</tr>
<tr style="height: 15pt;" height="20">
<td class="xl65" style="border-top: medium none; height: 15pt;" height="20">B</td>
<td class="xl66" style="border-top: medium none; border-left: medium none;">10</td>
</tr>
<tr style="height: 15pt;" height="20">
<td class="xl65" style="border-top: medium none; height: 15pt;" height="20">C</td>
<td class="xl66" style="border-top: medium none; border-left: medium none;">9</td>
</tr>
<tr style="height: 15pt;" height="20">
<td class="xl65" style="border-top: medium none; height: 15pt;" height="20">D</td>
<td class="xl66" style="border-top: medium none; border-left: medium none;">8</td>
</tr>
</tbody>
</table>
<p>So if you want a password of lowercase letters that provides the same level of protection as a more complicated password, you&#8217;ll need 12 characters.</p>
<p>Of course a password that is based on dictionary words is still not going to keep the bad guys at bay for long, it still needs to be a fairly random string of letters,  there are plenty of ways to come up with good passwords, but thats another article.</p>
<p>-Daniel</p>
]]></content:encoded>
			<wfw:commentRss>http://www.networklighthouse.com/2008/12/relative-password-strength/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
