<?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 for Simon Krauss, Privacy Eye</title>
	<atom:link href="http://simonkraussprivacyeye.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://simonkraussprivacyeye.com</link>
	<description>Thoughtful Privacy and Technology Investigations</description>
	<lastBuildDate>Fri, 17 Feb 2012 15:56:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on Do Generations View Online Privacy Differently? by Bobby Finkle</title>
		<link>http://simonkraussprivacyeye.com/2010/09/12/do-generations-view-online-privacy-differently/#comment-205</link>
		<dc:creator><![CDATA[Bobby Finkle]]></dc:creator>
		<pubDate>Fri, 17 Feb 2012 15:56:45 +0000</pubDate>
		<guid isPermaLink="false">http://simonkraussprivacyeye.com/?p=121#comment-205</guid>
		<description><![CDATA[I liked you&#039;re view on this, I talked about online privacy too check it out if you want.
http://bobbyloyalist.wordpress.com/wp-admin/post.php?post=88&amp;action=edit]]></description>
		<content:encoded><![CDATA[<p>I liked you&#8217;re view on this, I talked about online privacy too check it out if you want.<br />
<a href="http://bobbyloyalist.wordpress.com/wp-admin/post.php?post=88&#038;action=edit" rel="nofollow">http://bobbyloyalist.wordpress.com/wp-admin/post.php?post=88&#038;action=edit</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Should a Defendant be Compelled to Provide Prosecutor with Password to Encrypted Data? by Court Order to Turn Over Unencrypted Files not the Same as Order to Turn Over Password (Fricosu Revisited) &#171; Simon Krauss, Privacy Eye</title>
		<link>http://simonkraussprivacyeye.com/2012/01/08/should-a-defendant-be-compelled-to-provide-prosecutor-with-password/#comment-200</link>
		<dc:creator><![CDATA[Court Order to Turn Over Unencrypted Files not the Same as Order to Turn Over Password (Fricosu Revisited) &#171; Simon Krauss, Privacy Eye]]></dc:creator>
		<pubDate>Sun, 29 Jan 2012 23:03:31 +0000</pubDate>
		<guid isPermaLink="false">http://simonkraussprivacyeye.com/?p=413#comment-200</guid>
		<description><![CDATA[[...] In my first post of this year I commented on U.S. v. Ramona Camelia Fricosu, in which it was widely reported the government was trying to compel the Defendant to turn over the password to an encrypted hard drive found on a computer in her home. See: http://simonkraussprivacyeye.com/2012/01/08/should-a-defendant-be-compelled-to-provide-prosecutor-wi... [...]]]></description>
		<content:encoded><![CDATA[<p>[...] In my first post of this year I commented on U.S. v. Ramona Camelia Fricosu, in which it was widely reported the government was trying to compel the Defendant to turn over the password to an encrypted hard drive found on a computer in her home. See: <a href="http://simonkraussprivacyeye.com/2012/01/08/should-a-defendant-be-compelled-to-provide-prosecutor-wi" rel="nofollow">http://simonkraussprivacyeye.com/2012/01/08/should-a-defendant-be-compelled-to-provide-prosecutor-wi</a>&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Interesting Privacy Issues with Amazon&#8217;s Fire Tablet by slkrauss</title>
		<link>http://simonkraussprivacyeye.com/2011/10/09/interesting-privacy-issues-with-amazons-fire-tablet/#comment-128</link>
		<dc:creator><![CDATA[slkrauss]]></dc:creator>
		<pubDate>Mon, 10 Oct 2011 03:10:20 +0000</pubDate>
		<guid isPermaLink="false">http://simonkraussprivacyeye.com/?p=375#comment-128</guid>
		<description><![CDATA[You&#039;re right Fred, it is kind of like a Man-in-the-Middle security attack, in which someone intercepts messages between sender and recipient.  I guess the question in this case is whether the user is okay knowing the identity of the Man-in-the-Middle and whether there is full disclosure as to what Amazon will do with the data. 

The incidental anonimization may be a nice feature, but there is existing free servies that provide this function without serving as a Man-in-the-Middle.]]></description>
		<content:encoded><![CDATA[<p>You&#8217;re right Fred, it is kind of like a Man-in-the-Middle security attack, in which someone intercepts messages between sender and recipient.  I guess the question in this case is whether the user is okay knowing the identity of the Man-in-the-Middle and whether there is full disclosure as to what Amazon will do with the data. </p>
<p>The incidental anonimization may be a nice feature, but there is existing free servies that provide this function without serving as a Man-in-the-Middle.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Interesting Privacy Issues with Amazon&#8217;s Fire Tablet by Fred H Schlegel</title>
		<link>http://simonkraussprivacyeye.com/2011/10/09/interesting-privacy-issues-with-amazons-fire-tablet/#comment-127</link>
		<dc:creator><![CDATA[Fred H Schlegel]]></dc:creator>
		<pubDate>Sun, 09 Oct 2011 20:49:37 +0000</pubDate>
		<guid isPermaLink="false">http://simonkraussprivacyeye.com/?p=375#comment-127</guid>
		<description><![CDATA[I&#039;m trying to decide what to think of this.  If Silk provides a vpn of  to Amazon&#039;s servers it could actually increase privacy between you and unencrypted sites since the local ISP&#039;s would no longer be able to watch your actions.  Easier to &#039;trust&#039; Amazon than your local ISP - maybe.  Also very curious how they are going to deal with https and password accessible sites.  Sounds suspiciously like a man in the middle type strategy that would be very worrisome.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m trying to decide what to think of this.  If Silk provides a vpn of  to Amazon&#8217;s servers it could actually increase privacy between you and unencrypted sites since the local ISP&#8217;s would no longer be able to watch your actions.  Easier to &#8216;trust&#8217; Amazon than your local ISP &#8211; maybe.  Also very curious how they are going to deal with https and password accessible sites.  Sounds suspiciously like a man in the middle type strategy that would be very worrisome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on iPhones and iPads Track User Location &#8212; Is it Worth the Hysteria? by Fred H Schlegel</title>
		<link>http://simonkraussprivacyeye.com/2011/04/24/iphones-and-ipads-track-user-location-is-it-worth-the-hysteria/#comment-97</link>
		<dc:creator><![CDATA[Fred H Schlegel]]></dc:creator>
		<pubDate>Sun, 24 Apr 2011 13:47:42 +0000</pubDate>
		<guid isPermaLink="false">http://simonkraussprivacyeye.com/?p=312#comment-97</guid>
		<description><![CDATA[It is disconcerting that this unprotected file has been sitting around on my phone without my knowledge, however, I was aware that the information is nowhere near private for another reason. ATT and other providers all have access to this information by nature of the technology.  I believe this information is also sold to law enforcement (and maybe others) without need of a warrant.  

Finally, the idea that this information could ever be anonymized seems silly - I believe Google claims this concerning the location data they are gathering - Seems any forensics guy worth his salt could attach this type of file to an individual with minimal effort if they have some basic work and home location info to begin with.]]></description>
		<content:encoded><![CDATA[<p>It is disconcerting that this unprotected file has been sitting around on my phone without my knowledge, however, I was aware that the information is nowhere near private for another reason. ATT and other providers all have access to this information by nature of the technology.  I believe this information is also sold to law enforcement (and maybe others) without need of a warrant.  </p>
<p>Finally, the idea that this information could ever be anonymized seems silly &#8211; I believe Google claims this concerning the location data they are gathering &#8211; Seems any forensics guy worth his salt could attach this type of file to an individual with minimal effort if they have some basic work and home location info to begin with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to Identify Individuals from Social Security Numbers by slkrauss</title>
		<link>http://simonkraussprivacyeye.com/2011/03/06/how-to-identify-individuals-from-social-security-numbers/#comment-81</link>
		<dc:creator><![CDATA[slkrauss]]></dc:creator>
		<pubDate>Wed, 09 Mar 2011 14:19:59 +0000</pubDate>
		<guid isPermaLink="false">http://simonkraussprivacyeye.com/?p=287#comment-81</guid>
		<description><![CDATA[Since social security numbers are the only national unique identifier it is not surprising that it would be used for authentication in the U.S.  The problem is that, as you point out, it is/was not necessarily stored securely everywhere and, as the researchers point out, it can be cracked.

One answer is use two factor authentication (using something you have, such as a user name, and something you know secretly such as a PIN) or multi-factor authentication which would be two factor authentication plus adding &quot;something one is&quot; (such as biometrics).  

None of these methods of authentication will be useful in the long run if they are not stored securely, which is likely to happen with ubiquity of use. This requires  different types of authentication for access to different services.  This solution, however, creates complexity with having to remember multiple user names and passwords.  Lots of work going on a finding and marketing a better solution.]]></description>
		<content:encoded><![CDATA[<p>Since social security numbers are the only national unique identifier it is not surprising that it would be used for authentication in the U.S.  The problem is that, as you point out, it is/was not necessarily stored securely everywhere and, as the researchers point out, it can be cracked.</p>
<p>One answer is use two factor authentication (using something you have, such as a user name, and something you know secretly such as a PIN) or multi-factor authentication which would be two factor authentication plus adding &#8220;something one is&#8221; (such as biometrics).  </p>
<p>None of these methods of authentication will be useful in the long run if they are not stored securely, which is likely to happen with ubiquity of use. This requires  different types of authentication for access to different services.  This solution, however, creates complexity with having to remember multiple user names and passwords.  Lots of work going on a finding and marketing a better solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to Identify Individuals from Social Security Numbers by Fred H Schlegel</title>
		<link>http://simonkraussprivacyeye.com/2011/03/06/how-to-identify-individuals-from-social-security-numbers/#comment-80</link>
		<dc:creator><![CDATA[Fred H Schlegel]]></dc:creator>
		<pubDate>Tue, 08 Mar 2011 04:41:09 +0000</pubDate>
		<guid isPermaLink="false">http://simonkraussprivacyeye.com/?p=287#comment-80</guid>
		<description><![CDATA[I guess what surprises me at this point is that there is any assumption that the social security number is at all private.  So many banks, health care organizations, insurance companies, etc, have the number that it seems to have no value in proving identity at all.  Unfortunately, I&#039;m not sure what a satisfactory solution to the issue would be.]]></description>
		<content:encoded><![CDATA[<p>I guess what surprises me at this point is that there is any assumption that the social security number is at all private.  So many banks, health care organizations, insurance companies, etc, have the number that it seems to have no value in proving identity at all.  Unfortunately, I&#8217;m not sure what a satisfactory solution to the issue would be.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The FTC&#8217;s &#8220;Do Not Track&#8221; Solution &#8212; How will it Work? by slkrauss</title>
		<link>http://simonkraussprivacyeye.com/2010/12/05/the-ftcs-do-not-track-solution-how-will-it-work/#comment-48</link>
		<dc:creator><![CDATA[slkrauss]]></dc:creator>
		<pubDate>Mon, 06 Dec 2010 16:32:46 +0000</pubDate>
		<guid isPermaLink="false">http://simonkraussprivacyeye.com/?p=232#comment-48</guid>
		<description><![CDATA[Hi Fred,

I agree with you. It seems as though the FTC is seeking a middle ground between having &quot;no tracking&quot; as the default (which would be very disruptive), consumer opt out through a &quot;Do Not Track&quot; list, and what you suggest -- dealing with the harm of inapparopriate data usage.  The &quot;Do Not Track&quot; list does, however, provide a means to address the concerns of those who feel harmed by the online data collection itself.  The FTC acknowledges in its report that it had been too narrow in the past in looking at the privacy harms and is now considering being creeped out (my words) and reputation damage into its calculus.  I&#039;m wondering how today&#039;s brouhaha over &quot;history sniffing&quot; would fit with &quot;Do No Track.&quot;]]></description>
		<content:encoded><![CDATA[<p>Hi Fred,</p>
<p>I agree with you. It seems as though the FTC is seeking a middle ground between having &#8220;no tracking&#8221; as the default (which would be very disruptive), consumer opt out through a &#8220;Do Not Track&#8221; list, and what you suggest &#8212; dealing with the harm of inapparopriate data usage.  The &#8220;Do Not Track&#8221; list does, however, provide a means to address the concerns of those who feel harmed by the online data collection itself.  The FTC acknowledges in its report that it had been too narrow in the past in looking at the privacy harms and is now considering being creeped out (my words) and reputation damage into its calculus.  I&#8217;m wondering how today&#8217;s brouhaha over &#8220;history sniffing&#8221; would fit with &#8220;Do No Track.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The FTC&#8217;s &#8220;Do Not Track&#8221; Solution &#8212; How will it Work? by Fred H Schlegel</title>
		<link>http://simonkraussprivacyeye.com/2010/12/05/the-ftcs-do-not-track-solution-how-will-it-work/#comment-47</link>
		<dc:creator><![CDATA[Fred H Schlegel]]></dc:creator>
		<pubDate>Mon, 06 Dec 2010 03:22:15 +0000</pubDate>
		<guid isPermaLink="false">http://simonkraussprivacyeye.com/?p=232#comment-47</guid>
		<description><![CDATA[Hi Simon,  This really feels like a &#039;cat is out of the bag&#039; issue.  I&#039;d be more interested in legislation that deals with what can be done with the information once it is gathered rather than worrying that the tracking is going on.]]></description>
		<content:encoded><![CDATA[<p>Hi Simon,  This really feels like a &#8216;cat is out of the bag&#8217; issue.  I&#8217;d be more interested in legislation that deals with what can be done with the information once it is gathered rather than worrying that the tracking is going on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New &#8220;Good or Evil?&#8221; Privacy Graphic Is it Good or Evil? by Fred H Schlegel</title>
		<link>http://simonkraussprivacyeye.com/2010/10/26/new-good-or-evil-privacy-graphic-is-it-good-or-evil/#comment-28</link>
		<dc:creator><![CDATA[Fred H Schlegel]]></dc:creator>
		<pubDate>Wed, 27 Oct 2010 20:11:23 +0000</pubDate>
		<guid isPermaLink="false">http://simonkraussprivacyeye.com/?p=183#comment-28</guid>
		<description><![CDATA[The use of color made me think at first that the little people were indications of evil (red) and good (blue).  Tried to figure out why facebook was considered so good....]]></description>
		<content:encoded><![CDATA[<p>The use of color made me think at first that the little people were indications of evil (red) and good (blue).  Tried to figure out why facebook was considered so good&#8230;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

