<?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>Comments on: various stuffs</title>
	<atom:link href="http://www.reactivated.net/weblog/archives/2005/09/various-stuffs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.reactivated.net/weblog/archives/2005/09/various-stuffs/</link>
	<description>they got a skin and they put me in</description>
	<lastBuildDate>Mon, 06 Feb 2012 21:01:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: dsd&#8217;s weblog &#187; Blog Archive &#187; Digital Persona UareU Fingerprint Sensor driver for Linux</title>
		<link>http://www.reactivated.net/weblog/archives/2005/09/various-stuffs/comment-page-1/#comment-536</link>
		<dc:creator>dsd&#8217;s weblog &#187; Blog Archive &#187; Digital Persona UareU Fingerprint Sensor driver for Linux</dc:creator>
		<pubDate>Sat, 12 Nov 2005 12:43:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.reactivated.net/weblog/?p=60#comment-536</guid>
		<description>[...] I recently mentioned my new project of attempting to write a Linux driver for the &#8220;Microsoft Optical Desktop with Fingerprint Reader&#8221; keyboard. The keyboard works fine already (its just HID), but the fingerprint reader sensor requires its own driver, which I&#8217;m aiming to create. [...]</description>
		<content:encoded><![CDATA[<p>[...] I recently mentioned my new project of attempting to write a Linux driver for the &#8220;Microsoft Optical Desktop with Fingerprint Reader&#8221; keyboard. The keyboard works fine already (its just HID), but the fingerprint reader sensor requires its own driver, which I&#8217;m aiming to create. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fredrik</title>
		<link>http://www.reactivated.net/weblog/archives/2005/09/various-stuffs/comment-page-1/#comment-360</link>
		<dc:creator>Fredrik</dc:creator>
		<pubDate>Tue, 20 Sep 2005 15:42:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.reactivated.net/weblog/?p=60#comment-360</guid>
		<description>Regarding the fingerprint reader encryption algorithm, the XTEA algorithm could be a good first bet. I did some Googling, and found this (1) review, where some information regarding the security of Microsoft&#039;s standalone device is given. 

It wouldn&#039;t be far fetched to believe that the same hardware is used for Microsoft&#039;s standalone and keyboard combo fingerprint readers. 

The standalone units (at least) are apparently built by Digital Persona according to (2). Coincidentally, the information given about the security in (1) seems to be derived from blog comments in (2), where they describe the workings of an APC fingerprint reader and not the Microsoft one. The source of the information is shady as well, and I&#039;m not 100% sure the mechanics described make much sense.

Which is all a bit confusing. 

I haven&#039;t been able to find much information on who built the APC one (as I doubt they do anything besides buying an OEM reader and slapping their name one it) but then I didn&#039;t look very hard.

Anyway, Microsoft don&#039;t recommend using their fingerprint readers for serious security measures, which should mean that it isn&#039;t a tamper-resistant hardware platform with a signed key exchange, 256-bit AES encryption and a whole slew of bells and whistles added to that. I guess poking around the driver software would be the best option. Chances are the key is in there somewhere.

Hehe, I&#039;m not sure I made much sense above, bit may just be pointless drivel. I stumbled across your blog whilst at the Beagle site and killed some time Googling a subject which interests me (namely security). If I had a similar fingerprint reader myself, I&#039;d offer to help, but unfortunately I don&#039;t.

(1) - http://www.globetechnology.com/servlet/story/RTGAM.20041115.gtfingernov15/BNStory/TechReviews/
(2) - http://blogs.msdn.com/mswanson/archive/2004/12/03/274170.aspx</description>
		<content:encoded><![CDATA[<p>Regarding the fingerprint reader encryption algorithm, the XTEA algorithm could be a good first bet. I did some Googling, and found this (1) review, where some information regarding the security of Microsoft&#8217;s standalone device is given. </p>
<p>It wouldn&#8217;t be far fetched to believe that the same hardware is used for Microsoft&#8217;s standalone and keyboard combo fingerprint readers. </p>
<p>The standalone units (at least) are apparently built by Digital Persona according to (2). Coincidentally, the information given about the security in (1) seems to be derived from blog comments in (2), where they describe the workings of an APC fingerprint reader and not the Microsoft one. The source of the information is shady as well, and I&#8217;m not 100% sure the mechanics described make much sense.</p>
<p>Which is all a bit confusing. </p>
<p>I haven&#8217;t been able to find much information on who built the APC one (as I doubt they do anything besides buying an OEM reader and slapping their name one it) but then I didn&#8217;t look very hard.</p>
<p>Anyway, Microsoft don&#8217;t recommend using their fingerprint readers for serious security measures, which should mean that it isn&#8217;t a tamper-resistant hardware platform with a signed key exchange, 256-bit AES encryption and a whole slew of bells and whistles added to that. I guess poking around the driver software would be the best option. Chances are the key is in there somewhere.</p>
<p>Hehe, I&#8217;m not sure I made much sense above, bit may just be pointless drivel. I stumbled across your blog whilst at the Beagle site and killed some time Googling a subject which interests me (namely security). If I had a similar fingerprint reader myself, I&#8217;d offer to help, but unfortunately I don&#8217;t.</p>
<p>(1) &#8211; <a href="http://www.globetechnology.com/servlet/story/RTGAM.20041115.gtfingernov15/BNStory/TechReviews/" rel="nofollow">http://www.globetechnology.com/servlet/story/RTGAM.20041115.gtfingernov15/BNStory/TechReviews/</a><br />
(2) &#8211; <a href="http://blogs.msdn.com/mswanson/archive/2004/12/03/274170.aspx" rel="nofollow">http://blogs.msdn.com/mswanson/archive/2004/12/03/274170.aspx</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

