<?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: SPTP: Decentralized Single Sign-On</title>
	<atom:link href="http://zef.me/1099/sptp-decentralized-single-sign-on/feed" rel="self" type="application/rss+xml" />
	<link>http://zef.me/1099/sptp-decentralized-single-sign-on</link>
	<description>Technology, Me, You.</description>
	<lastBuildDate>Mon, 06 Sep 2010 22:06:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Bas Westerbaan</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-2473</link>
		<dc:creator>Bas Westerbaan</dc:creator>
		<pubDate>Wed, 17 Aug 2005 20:18:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-2473</guid>
		<description>&lt;p&gt;The problem is how to implement it with HTTP and HTML when a client-side RSA computation is required. Javascript isn&#039;t really an ideal language to do a RSA computation in. It would require activeX, flash or Java.. which isn&#039;t really &#039;complient&#039;.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>The problem is how to implement it with HTTP and HTML when a client-side RSA computation is required. Javascript isn&#8217;t really an ideal language to do a RSA computation in. It would require activeX, flash or Java.. which isn&#8217;t really &#8216;complient&#8217;.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Bas Westerbaan</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-6524</link>
		<dc:creator>Bas Westerbaan</dc:creator>
		<pubDate>Wed, 17 Aug 2005 20:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-6524</guid>
		<description>&lt;p&gt;The problem is how to implement it with HTTP and HTML when a client-side RSA computation is required. Javascript isn&#039;t really an ideal language to do a RSA computation in. It would require activeX, flash or Java.. which isn&#039;t really &#039;complient&#039;.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>The problem is how to implement it with HTTP and HTML when a client-side RSA computation is required. Javascript isn&#8217;t really an ideal language to do a RSA computation in. It would require activeX, flash or Java.. which isn&#8217;t really &#8216;complient&#8217;.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Shane Bauer</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-2472</link>
		<dc:creator>Shane Bauer</dc:creator>
		<pubDate>Tue, 16 Aug 2005 16:58:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-2472</guid>
		<description>&lt;p&gt;Ok. Well, fine. Just make it reliable enough so that people don&#039;t have to ever worry about public and private keys.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Ok. Well, fine. Just make it reliable enough so that people don&#8217;t have to ever worry about public and private keys.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Shane Bauer</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-6523</link>
		<dc:creator>Shane Bauer</dc:creator>
		<pubDate>Tue, 16 Aug 2005 16:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-6523</guid>
		<description>&lt;p&gt;Ok. Well, fine. Just make it reliable enough so that people don&#039;t have to ever worry about public and private keys.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Ok. Well, fine. Just make it reliable enough so that people don&#8217;t have to ever worry about public and private keys.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Bas Westerbaan</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-2471</link>
		<dc:creator>Bas Westerbaan</dc:creator>
		<pubDate>Tue, 16 Aug 2005 16:24:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-2471</guid>
		<description>&lt;p&gt;You don&#039;t have that problem, when - as i suggested already - use public/private RSA-like keypairs and you just challenge someone with a random string that can only be decrypted by you (the owner of the private key). There wouldn&#039;t be any login box required - as we know it.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>You don&#8217;t have that problem, when &#8211; as i suggested already &#8211; use public/private RSA-like keypairs and you just challenge someone with a random string that can only be decrypted by you (the owner of the private key). There wouldn&#8217;t be any login box required &#8211; as we know it.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Bas Westerbaan</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-6522</link>
		<dc:creator>Bas Westerbaan</dc:creator>
		<pubDate>Tue, 16 Aug 2005 16:24:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-6522</guid>
		<description>&lt;p&gt;You don&#039;t have that problem, when - as i suggested already - use public/private RSA-like keypairs and you just challenge someone with a random string that can only be decrypted by you (the owner of the private key). There wouldn&#039;t be any login box required - as we know it.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>You don&#8217;t have that problem, when &#8211; as i suggested already &#8211; use public/private RSA-like keypairs and you just challenge someone with a random string that can only be decrypted by you (the owner of the private key). There wouldn&#8217;t be any login box required &#8211; as we know it.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Shane Bauer</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-2470</link>
		<dc:creator>Shane Bauer</dc:creator>
		<pubDate>Mon, 15 Aug 2005 20:52:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-2470</guid>
		<description>&lt;p&gt;Not a bad idea, I don&#039;t think this would ever work, especially with the password problem.&lt;/p&gt;

&lt;p&gt;The only way I could imagine this would work is that each &quot;login&quot; site only asked for a username (i.e shane@zefhemel.com). That single site could then parse out the server and redirect them to the profile host where the user then types in the password. If successful, the profile host sends a response back to the original site containing a confirmation ID and username. Then some sort of verification code would need to be executed to ensure the confirmation ID was legit.&lt;/p&gt;

&lt;p&gt;Basically, it would work almost exactly like Passport, as login sites don&#039;t actually work with the username/password, but without a centralized server.&lt;/p&gt;

&lt;p&gt;Then you have to worry about login box cloaking and all sorts of other fraud activities.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Not a bad idea, I don&#8217;t think this would ever work, especially with the password problem.</p>

<p>The only way I could imagine this would work is that each &#8220;login&#8221; site only asked for a username (i.e <a href="mailto:shane@zefhemel.com">shane@zefhemel.com</a>). That single site could then parse out the server and redirect them to the profile host where the user then types in the password. If successful, the profile host sends a response back to the original site containing a confirmation ID and username. Then some sort of verification code would need to be executed to ensure the confirmation ID was legit.</p>

<p>Basically, it would work almost exactly like Passport, as login sites don&#8217;t actually work with the username/password, but without a centralized server.</p>

<p>Then you have to worry about login box cloaking and all sorts of other fraud activities.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Shane Bauer</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-6521</link>
		<dc:creator>Shane Bauer</dc:creator>
		<pubDate>Mon, 15 Aug 2005 20:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-6521</guid>
		<description>&lt;p&gt;Not a bad idea, I don&#039;t think this would ever work, especially with the password problem.&lt;/p&gt;

&lt;p&gt;The only way I could imagine this would work is that each &quot;login&quot; site only asked for a username (i.e shane@zefhemel.com). That single site could then parse out the server and redirect them to the profile host where the user then types in the password. If successful, the profile host sends a response back to the original site containing a confirmation ID and username. Then some sort of verification code would need to be executed to ensure the confirmation ID was legit.&lt;/p&gt;

&lt;p&gt;Basically, it would work almost exactly like Passport, as login sites don&#039;t actually work with the username/password, but without a centralized server.&lt;/p&gt;

&lt;p&gt;Then you have to worry about login box cloaking and all sorts of other fraud activities.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Not a bad idea, I don&#8217;t think this would ever work, especially with the password problem.</p>

<p>The only way I could imagine this would work is that each &#8220;login&#8221; site only asked for a username (i.e <a href="mailto:shane@zefhemel.com">shane@zefhemel.com</a>). That single site could then parse out the server and redirect them to the profile host where the user then types in the password. If successful, the profile host sends a response back to the original site containing a confirmation ID and username. Then some sort of verification code would need to be executed to ensure the confirmation ID was legit.</p>

<p>Basically, it would work almost exactly like Passport, as login sites don&#8217;t actually work with the username/password, but without a centralized server.</p>

<p>Then you have to worry about login box cloaking and all sorts of other fraud activities.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Gamyi</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-2469</link>
		<dc:creator>Sam Gamyi</dc:creator>
		<pubDate>Mon, 15 Aug 2005 08:55:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-2469</guid>
		<description>&lt;p&gt;Interesting idea.  For the travelling password problem, maybe it would be good that the system generates a unique -random- password for every signup.  So if forum &quot;A&quot; is unsecure and some script kiddie is able to know my password in this forum, that would be useless for gaining access to forum &quot;B&quot;, since the password would be different for that other forum.  (Sorry for my bad english).&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Interesting idea.  For the travelling password problem, maybe it would be good that the system generates a unique -random- password for every signup.  So if forum &#8220;A&#8221; is unsecure and some script kiddie is able to know my password in this forum, that would be useless for gaining access to forum &#8220;B&#8221;, since the password would be different for that other forum.  (Sorry for my bad english).</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Sam Gamyi</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-6520</link>
		<dc:creator>Sam Gamyi</dc:creator>
		<pubDate>Mon, 15 Aug 2005 08:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-6520</guid>
		<description>&lt;p&gt;Interesting idea.  For the travelling password problem, maybe it would be good that the system generates a unique -random- password for every signup.  So if forum &quot;A&quot; is unsecure and some script kiddie is able to know my password in this forum, that would be useless for gaining access to forum &quot;B&quot;, since the password would be different for that other forum.  (Sorry for my bad english).&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Interesting idea.  For the travelling password problem, maybe it would be good that the system generates a unique -random- password for every signup.  So if forum &#8220;A&#8221; is unsecure and some script kiddie is able to know my password in this forum, that would be useless for gaining access to forum &#8220;B&#8221;, since the password would be different for that other forum.  (Sorry for my bad english).</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Bas Westerbaan</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-2468</link>
		<dc:creator>Bas Westerbaan</dc:creator>
		<pubDate>Sat, 13 Aug 2005 18:23:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-2468</guid>
		<description>&lt;p&gt;I guess that every user has their own username on the final application like a message board. But their identity would be a public key; and best would be combined with an username@keyserver, which is easier to work with.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I guess that every user has their own username on the final application like a message board. But their identity would be a public key; and best would be combined with an username@keyserver, which is easier to work with.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Bas Westerbaan</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-6519</link>
		<dc:creator>Bas Westerbaan</dc:creator>
		<pubDate>Sat, 13 Aug 2005 18:23:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-6519</guid>
		<description>&lt;p&gt;I guess that every user has their own username on the final application like a message board. But their identity would be a public key; and best would be combined with an username@keyserver, which is easier to work with.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I guess that every user has their own username on the final application like a message board. But their identity would be a public key; and best would be combined with an username@keyserver, which is easier to work with.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Lewis</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-2467</link>
		<dc:creator>Lewis</dc:creator>
		<pubDate>Sat, 13 Aug 2005 17:37:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-2467</guid>
		<description>&lt;p&gt;What happens with clashing usernames? Surely people could just change data and get any username they want?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>What happens with clashing usernames? Surely people could just change data and get any username they want?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Lewis</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-6518</link>
		<dc:creator>Lewis</dc:creator>
		<pubDate>Sat, 13 Aug 2005 17:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-6518</guid>
		<description>&lt;p&gt;What happens with clashing usernames? Surely people could just change data and get any username they want?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>What happens with clashing usernames? Surely people could just change data and get any username they want?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Bas Westerbaan</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-2466</link>
		<dc:creator>Bas Westerbaan</dc:creator>
		<pubDate>Sat, 13 Aug 2005 17:02:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-2466</guid>
		<description>&lt;p&gt;It can be done way easier and way more secure:&lt;/p&gt;

&lt;p&gt;Everyone should have their own RSA-like keypair.
The only thing that has to be done to authenticate you is to challenge you to prove that you got the private key alongside the public one.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>It can be done way easier and way more secure:</p>

<p>Everyone should have their own RSA-like keypair.
The only thing that has to be done to authenticate you is to challenge you to prove that you got the private key alongside the public one.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Bas Westerbaan</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-6517</link>
		<dc:creator>Bas Westerbaan</dc:creator>
		<pubDate>Sat, 13 Aug 2005 17:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-6517</guid>
		<description>&lt;p&gt;It can be done way easier and way more secure:&lt;/p&gt;

&lt;p&gt;Everyone should have their own RSA-like keypair.
The only thing that has to be done to authenticate you is to challenge you to prove that you got the private key alongside the public one.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>It can be done way easier and way more secure:</p>

<p>Everyone should have their own RSA-like keypair.
The only thing that has to be done to authenticate you is to challenge you to prove that you got the private key alongside the public one.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-2465</link>
		<dc:creator>David</dc:creator>
		<pubDate>Sat, 13 Aug 2005 16:25:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-2465</guid>
		<description>&lt;p&gt;Have you looked at OpenID and Lid yet?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Have you looked at OpenID and Lid yet?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-6516</link>
		<dc:creator>David</dc:creator>
		<pubDate>Sat, 13 Aug 2005 16:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-6516</guid>
		<description>&lt;p&gt;Have you looked at OpenID and Lid yet?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Have you looked at OpenID and Lid yet?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Cow</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-2464</link>
		<dc:creator>Cow</dc:creator>
		<pubDate>Sat, 13 Aug 2005 15:54:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-2464</guid>
		<description>&lt;p&gt;Sounds very similar to Drupal&#039;s distributed login.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Sounds very similar to Drupal&#8217;s distributed login.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Cow</title>
		<link>http://zef.me/1099/sptp-decentralized-single-sign-on/comment-page-1#comment-6515</link>
		<dc:creator>Cow</dc:creator>
		<pubDate>Sat, 13 Aug 2005 15:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zefhemel.com/archives/2005/08/13/sptp-decentralized-single-sign-on#comment-6515</guid>
		<description>&lt;p&gt;Sounds very similar to Drupal&#039;s distributed login.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Sounds very similar to Drupal&#8217;s distributed login.</p>]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->