<?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: Protecting Your Users&#8217; Data with a Privacy Wall</title>
	<atom:link href="http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/</link>
	<description>(intr.v.) 1. To waste time; trifle. 2. To talk nonsense. (n.) Nonsense; foolishness</description>
	<lastBuildDate>Tue, 19 Jan 2010 14:46:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Safeguarding Your Data: The Privacy Wall &#171; Wesabe: Your Money. Your Community.</title>
		<link>http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/comment-page-1/#comment-1221</link>
		<dc:creator>Safeguarding Your Data: The Privacy Wall &#171; Wesabe: Your Money. Your Community.</dc:creator>
		<pubDate>Wed, 18 Nov 2009 03:27:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/#comment-1221</guid>
		<description>[...] like something a bit more technical, along with ways to attack the wall, I&#8217;ve posted a longer article over on my personal [...]</description>
		<content:encoded><![CDATA[<p>[...] like something a bit more technical, along with ways to attack the wall, I&#8217;ve posted a longer article over on my personal [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/comment-page-1/#comment-1218</link>
		<dc:creator>David</dc:creator>
		<pubDate>Mon, 05 Oct 2009 21:18:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/#comment-1218</guid>
		<description>Brad-

The only thing I could think would need a change to the OpenID spec.

Along with the user&#039;s OpenID would be sent some random (but consistent) secret. Each user would get a different value.

Then that secret could be used to index the user&#039;s private data in the database.

Not sure there&#039;s much chance in getting that accepted though.</description>
		<content:encoded><![CDATA[<p>Brad-</p>
<p>The only thing I could think would need a change to the OpenID spec.</p>
<p>Along with the user&#8217;s OpenID would be sent some random (but consistent) secret. Each user would get a different value.</p>
<p>Then that secret could be used to index the user&#8217;s private data in the database.</p>
<p>Not sure there&#8217;s much chance in getting that accepted though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brad</title>
		<link>http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/comment-page-1/#comment-1217</link>
		<dc:creator>brad</dc:creator>
		<pubDate>Mon, 05 Oct 2009 20:36:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/#comment-1217</guid>
		<description>Good question, David. There really needs to be some secret that is not stored on the server-side in order for this to work, so it&#039;s not a great fit for things like OpenID or OAuth.

You could ask the user to create a secondary password, although that kind of defeats the purpose of OpenID.

You could set a cookie with a generated secret when the user first signs up, but that&#039;s going to stop working if the user changes browsers or clears their cookies. You could also send that secret to them via email, telling them that they&#039;ll need it should they use another browser or clear their cookies, but that&#039;s still not very user-friendly.

This might make for a good follow-up post. If you have any ideas on it, let me know.</description>
		<content:encoded><![CDATA[<p>Good question, David. There really needs to be some secret that is not stored on the server-side in order for this to work, so it&#8217;s not a great fit for things like OpenID or OAuth.</p>
<p>You could ask the user to create a secondary password, although that kind of defeats the purpose of OpenID.</p>
<p>You could set a cookie with a generated secret when the user first signs up, but that&#8217;s going to stop working if the user changes browsers or clears their cookies. You could also send that secret to them via email, telling them that they&#8217;ll need it should they use another browser or clear their cookies, but that&#8217;s still not very user-friendly.</p>
<p>This might make for a good follow-up post. If you have any ideas on it, let me know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/comment-page-1/#comment-1216</link>
		<dc:creator>David</dc:creator>
		<pubDate>Mon, 05 Oct 2009 19:39:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/#comment-1216</guid>
		<description>Nice article.

Got any ideas for when I don&#039;t have anything that only the user knows?

I&#039;m authenticating using OpenID, so I only get the user&#039;s OpenID - no password or anything only known to the user (the OpenID is by its nature public).</description>
		<content:encoded><![CDATA[<p>Nice article.</p>
<p>Got any ideas for when I don&#8217;t have anything that only the user knows?</p>
<p>I&#8217;m authenticating using OpenID, so I only get the user&#8217;s OpenID &#8211; no password or anything only known to the user (the OpenID is by its nature public).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sınıf öğretmeni</title>
		<link>http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/comment-page-1/#comment-1203</link>
		<dc:creator>sınıf öğretmeni</dc:creator>
		<pubDate>Tue, 03 Feb 2009 20:24:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/#comment-1203</guid>
		<description>thanks, great article.</description>
		<content:encoded><![CDATA[<p>thanks, great article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajanslar</title>
		<link>http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/comment-page-1/#comment-1201</link>
		<dc:creator>Ajanslar</dc:creator>
		<pubDate>Fri, 30 Jan 2009 14:45:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/#comment-1201</guid>
		<description>Wonderful article. I’m interested in this subject and want to learn more. Privacy wall is so important. Thank you</description>
		<content:encoded><![CDATA[<p>Wonderful article. I’m interested in this subject and want to learn more. Privacy wall is so important. Thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: boyaci</title>
		<link>http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/comment-page-1/#comment-1200</link>
		<dc:creator>boyaci</dc:creator>
		<pubDate>Tue, 20 Jan 2009 18:44:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/#comment-1200</guid>
		<description>Ninja Privacy Techniques” was on one-way hashes which is ancient (in computer terms), but the privacy wall techniques they’re both implementing and educating around are beautifully simple, and pressingly</description>
		<content:encoded><![CDATA[<p>Ninja Privacy Techniques” was on one-way hashes which is ancient (in computer terms), but the privacy wall techniques they’re both implementing and educating around are beautifully simple, and pressingly</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nick</title>
		<link>http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/comment-page-1/#comment-1197</link>
		<dc:creator>nick</dc:creator>
		<pubDate>Fri, 02 Jan 2009 16:09:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/#comment-1197</guid>
		<description>thanx</description>
		<content:encoded><![CDATA[<p>thanx</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aşk şiirleri</title>
		<link>http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/comment-page-1/#comment-1189</link>
		<dc:creator>aşk şiirleri</dc:creator>
		<pubDate>Wed, 19 Nov 2008 12:33:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/#comment-1189</guid>
		<description>[...] footle » Protecting Your Users’ Data with a Privacy Wall. the privacy scheme is pretty obvious but they have some good tips on other production problems that come up. [...]</description>
		<content:encoded><![CDATA[<p>[...] footle » Protecting Your Users’ Data with a Privacy Wall. the privacy scheme is pretty obvious but they have some good tips on other production problems that come up. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oil painting reproductions</title>
		<link>http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/comment-page-1/#comment-1152</link>
		<dc:creator>oil painting reproductions</dc:creator>
		<pubDate>Thu, 17 Jul 2008 08:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.footle.org/2007/02/22/protecting-your-users-data-with-a-privacy-wall/#comment-1152</guid>
		<description>We’re presently setting up a server for a small call center.  The client wishes to upload all call recordings through FTP to his own server file.  At this point, I’ve already detected a server hole.  In this case, how can your discussion help us?  How can we implement it to our server or system?</description>
		<content:encoded><![CDATA[<p>We’re presently setting up a server for a small call center.  The client wishes to upload all call recordings through FTP to his own server file.  At this point, I’ve already detected a server hole.  In this case, how can your discussion help us?  How can we implement it to our server or system?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
