<?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>Biogy &#187; Articles</title>
	<atom:link href="http://www.biogy.com/category/news/articles/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.biogy.com</link>
	<description>Identify yourself securely</description>
	<lastBuildDate>Thu, 28 Apr 2011 06:54:51 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Global Security Challenge Finalists Announced</title>
		<link>http://www.biogy.com/2010/10/global-security-challenge-finalists-announced/</link>
		<comments>http://www.biogy.com/2010/10/global-security-challenge-finalists-announced/#comments</comments>
		<pubDate>Sun, 31 Oct 2010 08:27:10 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.biogy.com/?p=105</guid>
		<description><![CDATA[The Global Security Challenge will see companies from around the globe enter the finals for security innovation development funding.]]></description>
			<content:encoded><![CDATA[<p>As the Global Security Challenge approaches, the Biogy team is preparing for an exciting trip to London.  The article below does a great job of explaining the GSC competition and what we&#8217;re up against in the coming month.</p>
<p><a href="http://www.prosecurityzone.com/Customisation/News/Education_Training_and_Professional_Services/Exhibitions_and_Trade_Shows/Global_Security_Challenge_Finalists_Announced.asp">Global Security Challenge Finalists Announced</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.biogy.com/2010/10/global-security-challenge-finalists-announced/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Password Security</title>
		<link>http://www.biogy.com/2010/02/password-security/</link>
		<comments>http://www.biogy.com/2010/02/password-security/#comments</comments>
		<pubDate>Fri, 26 Feb 2010 12:31:43 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Password]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.biogy.com/?p=6</guid>
		<description><![CDATA[There is an interesting investigation into an issue with a GoDaddy hosted website. The investigation touches on a number of different things but one of them is that GoDaddy stores passwords without hashing them.
I did my undergraduate computer science degree in the early 1970s and even then we were taught that passwords should always be hashed (we called them one-way-ciphers back then). Instead of comparing the actual password to whatever was typed, the typed password<a href="http://www.biogy.com/2010/02/password-security/">&#160;Read more...</a>]]></description>
			<content:encoded><![CDATA[<p>There is an interesting investigation into an <a href="http://blog.sucuri.net/2010/02/godaddy-store-your-passwords-in-clear.html">issue with a GoDaddy hosted website</a>. The investigation touches on a number of different things but one of them is that GoDaddy stores passwords without hashing them.</p>
<p>I did my undergraduate computer science degree in the early 1970s and even then we were taught that passwords should always be hashed (we called them one-way-ciphers back then). Instead of comparing the actual password to whatever was typed, the typed password was hashed and compared to the stored hashed password. In this way, even if the password file was compromised, it was impossible to recover the passwords.</p>
<p>As computers got faster, <a href="http://docstore.mik.ua/orelly/networking/puis/ch08_06.htm">two changes got made most publicly in the Unix operating system</a>.  Firstly, the encryption algorithm needed to become computationally expensive, unlike most encryption where efficiency is one of the goals. Secondly, a salt was stored along with the password. These two changes made it intractable, at least for a time, to pre-compute hashed values for an entire dictionary or for all possible passwords.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.biogy.com/2010/02/password-security/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>NIST Certified USB Drives Cracked</title>
		<link>http://www.biogy.com/2010/02/nist-certified-usb-drives-cracked/</link>
		<comments>http://www.biogy.com/2010/02/nist-certified-usb-drives-cracked/#comments</comments>
		<pubDate>Fri, 26 Feb 2010 12:18:06 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Certified]]></category>
		<category><![CDATA[Drives]]></category>
		<category><![CDATA[USB]]></category>

		<guid isPermaLink="false">http://www.biogy.com/?p=1</guid>
		<description><![CDATA[Three NIST certified USB drives (those from Kingston, Sandisk and Verbatim) have been cracked. It turns out that the protocol for communicating between the password checking software on the host, and the encryption engine on the drive itself was very naively implemented. A fixed string was sent from the host to the drive to indicate that the password had been entered correctly and so to unlock the drive. Of course, any other mechanism for sending<a href="http://www.biogy.com/2010/02/nist-certified-usb-drives-cracked/">&#160;Read more...</a>]]></description>
			<content:encoded><![CDATA[<p>Three NIST certified USB drives (those from Kingston, Sandisk and Verbatim) have been cracked. It turns out that the protocol for communicating between the password checking software on the host, and the encryption engine on the drive itself was very naively implemented. A fixed string was sent from the host to the drive to indicate that the password had been entered correctly and so to unlock the drive. Of course, any other mechanism for sending the appropriate string to the device would work just as well and so unlock the drive without the necessity for knowing the password.</p>
<p>The best solution to this is to perform all the authentication on the drive itself, as Biogy does on its personal data vault. But even if authentication is done on the host, there is a requirement for a protocol to unlock the drive that is not vulnerable to a simple replay.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.biogy.com/2010/02/nist-certified-usb-drives-cracked/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

