<?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: Good Morning: Time to Change Your Button</title>
	<atom:link href="http://blog.passpack.com/2008/06/good-morning-time-to-change-your-button/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.passpack.com/2008/06/good-morning-time-to-change-your-button/</link>
	<description>Passpack keeps your logins safe, organized and available 24/7. You can share passwords with your team in 100% privacy.</description>
	<lastBuildDate>Fri, 10 May 2013 18:12:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4</generator>
	<item>
		<title>By: Tara</title>
		<link>http://blog.passpack.com/2008/06/good-morning-time-to-change-your-button/comment-page-1/#comment-497</link>
		<dc:creator>Tara</dc:creator>
		<pubDate>Tue, 24 Jun 2008 13:42:23 +0000</pubDate>
		<guid isPermaLink="false">http://passpack.wordpress.com/?p=491#comment-497</guid>
		<description>@tom
Yes, I will attempt to make pre-notification in the future. :)</description>
		<content:encoded><![CDATA[<p>@tom<br />
Yes, I will attempt to make pre-notification in the future. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tom</title>
		<link>http://blog.passpack.com/2008/06/good-morning-time-to-change-your-button/comment-page-1/#comment-505</link>
		<dc:creator>tom</dc:creator>
		<pubDate>Fri, 20 Jun 2008 09:02:29 +0000</pubDate>
		<guid isPermaLink="false">http://passpack.wordpress.com/?p=491#comment-505</guid>
		<description>RE: http://passpack.wordpress.com/2008/06/16/good-morning-time-to-change-your-button/#comment-9278
that is a pretty good description, and it sounds like a good update. some advance warning would have been helpful in case of compatibility problems, but if any security improvements can be made it is generally nice to have them implemented quick as possible so... =P</description>
		<content:encoded><![CDATA[<p>RE: <a href="http://passpack.wordpress.com/2008/06/16/good-morning-time-to-change-your-button/#comment-9278" rel="nofollow">http://passpack.wordpress.com/2008/06/16/good-morning-time-to-change-your-button/#comment-9278</a><br />
that is a pretty good description, and it sounds like a good update. some advance warning would have been helpful in case of compatibility problems, but if any security improvements can be made it is generally nice to have them implemented quick as possible so&#8230; =P</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tara</title>
		<link>http://blog.passpack.com/2008/06/good-morning-time-to-change-your-button/comment-page-1/#comment-504</link>
		<dc:creator>Tara</dc:creator>
		<pubDate>Wed, 18 Jun 2008 15:07:37 +0000</pubDate>
		<guid isPermaLink="false">http://passpack.wordpress.com/?p=491#comment-504</guid>
		<description>@ibc
I can understand that. Yes, it&#039;s standard legalese, but actually we will allow financial data with the paid packages once they are ready.</description>
		<content:encoded><![CDATA[<p>@ibc<br />
I can understand that. Yes, it&#8217;s standard legalese, but actually we will allow financial data with the paid packages once they are ready.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ibc</title>
		<link>http://blog.passpack.com/2008/06/good-morning-time-to-change-your-button/comment-page-1/#comment-503</link>
		<dc:creator>ibc</dc:creator>
		<pubDate>Wed, 18 Jun 2008 14:20:54 +0000</pubDate>
		<guid isPermaLink="false">http://passpack.wordpress.com/?p=491#comment-503</guid>
		<description>This is the part of Passpack that frightens me (from the &quot;Terms and Conditions&quot; page):

&lt;i&gt;Furthermore it is forbidden to store critical data such as, but not limited to, financial data or access data to financial institutions, or any data which, if lost, stolen or destroyed, could result in personal or public catastrophe.&lt;/i&gt;

I realize this is just legal boilerplate, but it&#039;s quite sobering anyway.  Looking forward to the day that there&#039;s a solution that doesn&#039;t need the above caveat.</description>
		<content:encoded><![CDATA[<p>This is the part of Passpack that frightens me (from the &#8220;Terms and Conditions&#8221; page):</p>
<p><i>Furthermore it is forbidden to store critical data such as, but not limited to, financial data or access data to financial institutions, or any data which, if lost, stolen or destroyed, could result in personal or public catastrophe.</i></p>
<p>I realize this is just legal boilerplate, but it&#8217;s quite sobering anyway.  Looking forward to the day that there&#8217;s a solution that doesn&#8217;t need the above caveat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tara</title>
		<link>http://blog.passpack.com/2008/06/good-morning-time-to-change-your-button/comment-page-1/#comment-502</link>
		<dc:creator>Tara</dc:creator>
		<pubDate>Mon, 16 Jun 2008 21:02:51 +0000</pubDate>
		<guid isPermaLink="false">http://passpack.wordpress.com/?p=491#comment-502</guid>
		<description>@Saniul
He added an encrypted authentication token associated with the domain that lets the button authenticate itself to the server so that the server knows that it&#039;s OK to reply with the encrypted login data. If the token is incorrect or missing, the server will ignore the login request.

Just want to underline:

The &quot;login data&quot; that the server replies with is now, has always been, and always will be, encrypted with a AES-256. So even if a fraudulent attempt were made (prior to last night&#039;s change) the fraudster would have still found himself with an encrypted jumble that he would have had to brute force attack (which is considered &quot;uncrackable&quot;). But that bothered Francesco, so he put up this additional barrier so that a fraudster wouldn&#039;t even get his hands on the encrypted data to begin with.

Also, the attack that the fraudster would have to put together would have been fairly complex and aimed at a single person.

I hope that makes sense :) I&#039;ll see if we can&#039;t get a detailed description of the process written for you.</description>
		<content:encoded><![CDATA[<p>@Saniul<br />
He added an encrypted authentication token associated with the domain that lets the button authenticate itself to the server so that the server knows that it&#8217;s OK to reply with the encrypted login data. If the token is incorrect or missing, the server will ignore the login request.</p>
<p>Just want to underline:</p>
<p>The &#8220;login data&#8221; that the server replies with is now, has always been, and always will be, encrypted with a AES-256. So even if a fraudulent attempt were made (prior to last night&#8217;s change) the fraudster would have still found himself with an encrypted jumble that he would have had to brute force attack (which is considered &#8220;uncrackable&#8221;). But that bothered Francesco, so he put up this additional barrier so that a fraudster wouldn&#8217;t even get his hands on the encrypted data to begin with.</p>
<p>Also, the attack that the fraudster would have to put together would have been fairly complex and aimed at a single person.</p>
<p>I hope that makes sense :) I&#8217;ll see if we can&#8217;t get a detailed description of the process written for you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared</title>
		<link>http://blog.passpack.com/2008/06/good-morning-time-to-change-your-button/comment-page-1/#comment-501</link>
		<dc:creator>Jared</dc:creator>
		<pubDate>Mon, 16 Jun 2008 20:34:27 +0000</pubDate>
		<guid isPermaLink="false">http://passpack.wordpress.com/?p=491#comment-501</guid>
		<description>I am having the same problem, although I have only tried it on a couple of sites. Facebook worked with the button perfectly before but now its not working since the update. (Safari 3.1.1, OSX 10.5.3)</description>
		<content:encoded><![CDATA[<p>I am having the same problem, although I have only tried it on a couple of sites. Facebook worked with the button perfectly before but now its not working since the update. (Safari 3.1.1, OSX 10.5.3)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tara</title>
		<link>http://blog.passpack.com/2008/06/good-morning-time-to-change-your-button/comment-page-1/#comment-500</link>
		<dc:creator>Tara</dc:creator>
		<pubDate>Mon, 16 Jun 2008 15:25:27 +0000</pubDate>
		<guid isPermaLink="false">http://passpack.wordpress.com/?p=491#comment-500</guid>
		<description>@Sanuil
I&#039;m writing a reply for you... just a moment.

@Clemens
Sending you an email.</description>
		<content:encoded><![CDATA[<p>@Sanuil<br />
I&#8217;m writing a reply for you&#8230; just a moment.</p>
<p>@Clemens<br />
Sending you an email.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clemens</title>
		<link>http://blog.passpack.com/2008/06/good-morning-time-to-change-your-button/comment-page-1/#comment-499</link>
		<dc:creator>Clemens</dc:creator>
		<pubDate>Mon, 16 Jun 2008 15:09:26 +0000</pubDate>
		<guid isPermaLink="false">http://passpack.wordpress.com/?p=491#comment-499</guid>
		<description>The new button doesn&#039;t work for me. (Firefox 2.0.0.14 Vista SP 0 and XP SP3)</description>
		<content:encoded><![CDATA[<p>The new button doesn&#8217;t work for me. (Firefox 2.0.0.14 Vista SP 0 and XP SP3)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saniul</title>
		<link>http://blog.passpack.com/2008/06/good-morning-time-to-change-your-button/comment-page-1/#comment-498</link>
		<dc:creator>Saniul</dc:creator>
		<pubDate>Mon, 16 Jun 2008 13:54:34 +0000</pubDate>
		<guid isPermaLink="false">http://passpack.wordpress.com/?p=491#comment-498</guid>
		<description>What did he change? :)</description>
		<content:encoded><![CDATA[<p>What did he change? :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
