<?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 for quuxlabs</title>
	<atom:link href="http://www.quuxlabs.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.quuxlabs.com</link>
	<description>transmuting ideas into value</description>
	<lastBuildDate>Sun, 13 Feb 2011 17:15:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Paper Token: Gutenberg&#8217;s version of One Time Passwords by Alexandre Dulaunoy</title>
		<link>http://www.quuxlabs.com/blog/2010/09/paper-token-gutenbergs-version-of-one-time-passwords/comment-page-1/#comment-804</link>
		<dc:creator>Alexandre Dulaunoy</dc:creator>
		<pubDate>Sun, 13 Feb 2011 17:15:42 +0000</pubDate>
		<guid isPermaLink="false">http://www2.quuxlabs.com/?p=431#comment-804</guid>
		<description>Thank you for your comment.

It&#039;s true that S/KEY exists for years and used by a small number of people. The article is more targeting the HOTP[1] devices (e.g. RSA SecurID token) where a lot of services are now relying on token-based hardware to access &quot;secure&quot; services. As the majority of token user (or even administrator) didn&#039;t know  that event-based token can be pre-calculated and printed on a sheet of paper, we show this possibility for HOTP. Especially that large corporation use token-based access for emergency case, they usually don&#039;t need the hardware-based token (usually more expensive to acquire and manage) and could simply rely on a paper.

I hope this answers your question.

[1] http://tools.ietf.org/html/rfc4226</description>
		<content:encoded><![CDATA[<p>Thank you for your comment.</p>
<p>It&#8217;s true that S/KEY exists for years and used by a small number of people. The article is more targeting the HOTP[1] devices (e.g. RSA SecurID token) where a lot of services are now relying on token-based hardware to access &#8220;secure&#8221; services. As the majority of token user (or even administrator) didn&#8217;t know  that event-based token can be pre-calculated and printed on a sheet of paper, we show this possibility for HOTP. Especially that large corporation use token-based access for emergency case, they usually don&#8217;t need the hardware-based token (usually more expensive to acquire and manage) and could simply rely on a paper.</p>
<p>I hope this answers your question.</p>
<p>[1] <a href="http://tools.ietf.org/html/rfc4226" rel="nofollow">http://tools.ietf.org/html/rfc4226</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Paper Token: Gutenberg&#8217;s version of One Time Passwords by none</title>
		<link>http://www.quuxlabs.com/blog/2010/09/paper-token-gutenbergs-version-of-one-time-passwords/comment-page-1/#comment-753</link>
		<dc:creator>none</dc:creator>
		<pubDate>Mon, 07 Feb 2011 12:00:42 +0000</pubDate>
		<guid isPermaLink="false">http://www2.quuxlabs.com/?p=431#comment-753</guid>
		<description>I don&#039;t *quite* get the point. From a cursory glance, OPIE - S/KEY already supports the concept of having a printed list of pregenerated one-time-use passwords, and people (albeit maybe not enough people) have been using it in this way for years, so what exactly is the new thing in this article? What does your new implementation bring?</description>
		<content:encoded><![CDATA[<p>I don&#8217;t *quite* get the point. From a cursory glance, OPIE &#8211; S/KEY already supports the concept of having a printed list of pregenerated one-time-use passwords, and people (albeit maybe not enough people) have been using it in this way for years, so what exactly is the new thing in this article? What does your new implementation bring?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Location and Friendship: Data Mining in Facebook by Edith</title>
		<link>http://www.quuxlabs.com/blog/2010/09/location-and-friendship-data-mining-in-facebook/comment-page-1/#comment-8</link>
		<dc:creator>Edith</dc:creator>
		<pubDate>Wed, 08 Sep 2010 00:02:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.quuxlabs.com/?p=598#comment-8</guid>
		<description>Thank you for the sharing. It is a really interesting study!</description>
		<content:encoded><![CDATA[<p>Thank you for the sharing. It is a really interesting study!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

