<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Extra tokens are convenient</title>
	<atom:link href="http://blog.trustbearer.com/2008/05/01/extra-tokens-are-convenient/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.trustbearer.com/2008/05/01/extra-tokens-are-convenient/</link>
	<description>A Convenient and Secure Connection to the Web</description>
	<lastBuildDate>Sat, 24 Apr 2010 07:42:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Billy</title>
		<link>http://blog.trustbearer.com/2008/05/01/extra-tokens-are-convenient/#comment-41</link>
		<dc:creator>Billy</dc:creator>
		<pubDate>Wed, 18 Jun 2008 01:24:35 +0000</pubDate>
		<guid isPermaLink="false">http://openidtrustbearer.wordpress.com/?p=36#comment-41</guid>
		<description>One big upside to the phonefactor-type solution is the Out of Band component.  It would be great if your solution didn&#039;t essentially translate the &quot;what you have&quot; into a &quot;what you know&quot; and then require the user to feed it into the browser, where phishing can occur.</description>
		<content:encoded><![CDATA[<p>One big upside to the phonefactor-type solution is the Out of Band component.  It would be great if your solution didn&#8217;t essentially translate the &#8220;what you have&#8221; into a &#8220;what you know&#8221; and then require the user to feed it into the browser, where phishing can occur.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashwin</title>
		<link>http://blog.trustbearer.com/2008/05/01/extra-tokens-are-convenient/#comment-40</link>
		<dc:creator>Ashwin</dc:creator>
		<pubDate>Sun, 15 Jun 2008 03:20:25 +0000</pubDate>
		<guid isPermaLink="false">http://openidtrustbearer.wordpress.com/?p=36#comment-40</guid>
		<description>Thanks Brian, I&#039;ve looked at a variety of these (i.e. PhoneFactor).  Seems like (though I don&#039;t fully understand this stuff) they focus on placing a call rather than establishing some sort of data session, which seems like it could be a common technical solution without regard for differences between telephone networks.  Would love to stick with your stuf though...</description>
		<content:encoded><![CDATA[<p>Thanks Brian, I&#8217;ve looked at a variety of these (i.e. PhoneFactor).  Seems like (though I don&#8217;t fully understand this stuff) they focus on placing a call rather than establishing some sort of data session, which seems like it could be a common technical solution without regard for differences between telephone networks.  Would love to stick with your stuf though&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Kelly</title>
		<link>http://blog.trustbearer.com/2008/05/01/extra-tokens-are-convenient/#comment-39</link>
		<dc:creator>Brian Kelly</dc:creator>
		<pubDate>Mon, 09 Jun 2008 13:01:27 +0000</pubDate>
		<guid isPermaLink="false">http://openidtrustbearer.wordpress.com/?p=36#comment-39</guid>
		<description>We are considering a few alternative tokens from the traditional ones that we&#039;ve supported in the past. This includes mobile phones and soft tokens. One of the challenges in the mobile phone space is a standard for communication between the host computer and the mobile phone, but we&#039;re &lt;a href=&quot;http://en.wikipedia.org/wiki/Near_Field_Communication&quot; rel=&quot;nofollow&quot;&gt;getting there&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>We are considering a few alternative tokens from the traditional ones that we&#8217;ve supported in the past. This includes mobile phones and soft tokens. One of the challenges in the mobile phone space is a standard for communication between the host computer and the mobile phone, but we&#8217;re <a href="http://en.wikipedia.org/wiki/Near_Field_Communication" rel="nofollow">getting there</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashwin</title>
		<link>http://blog.trustbearer.com/2008/05/01/extra-tokens-are-convenient/#comment-38</link>
		<dc:creator>Ashwin</dc:creator>
		<pubDate>Sun, 08 Jun 2008 23:43:21 +0000</pubDate>
		<guid isPermaLink="false">http://openidtrustbearer.wordpress.com/?p=36#comment-38</guid>
		<description>Word.  Lots of benefits.  First, no need to distribute or manage physical tokens.  Second, 2nd factor authentication could occur out of band, which could protect against lots of man in the middle and phishing.  Are there any non-token Trustbearer services on tap?</description>
		<content:encoded><![CDATA[<p>Word.  Lots of benefits.  First, no need to distribute or manage physical tokens.  Second, 2nd factor authentication could occur out of band, which could protect against lots of man in the middle and phishing.  Are there any non-token Trustbearer services on tap?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sergey</title>
		<link>http://blog.trustbearer.com/2008/05/01/extra-tokens-are-convenient/#comment-37</link>
		<dc:creator>Sergey</dc:creator>
		<pubDate>Sat, 07 Jun 2008 17:26:14 +0000</pubDate>
		<guid isPermaLink="false">http://openidtrustbearer.wordpress.com/?p=36#comment-37</guid>
		<description>I&#039;m wondering why you are sticking with the physical token concept.  Why not evolve strong authentication towards usage of physical devices already in the hands of consumers, such as a mobile phone?</description>
		<content:encoded><![CDATA[<p>I&#8217;m wondering why you are sticking with the physical token concept.  Why not evolve strong authentication towards usage of physical devices already in the hands of consumers, such as a mobile phone?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
