<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Passpack Blog &#187; 1click login</title>
	<atom:link href="http://blog.passpack.com/tag/1click-login/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.passpack.com</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, 20 Aug 2010 16:17:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>FIXED: 1 Click Login Button</title>
		<link>http://blog.passpack.com/2008/10/reinstall-1click-login-button/</link>
		<comments>http://blog.passpack.com/2008/10/reinstall-1click-login-button/#comments</comments>
		<pubDate>Sat, 11 Oct 2008 11:19:36 +0000</pubDate>
		<dc:creator>Louise</dc:creator>
				<category><![CDATA[Maintenance]]></category>
		<category><![CDATA[1click login]]></category>
		<category><![CDATA[passpack]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[update]]></category>

		<guid isPermaLink="false">http://passpack.wordpress.com/?p=1456</guid>
		<description><![CDATA[We were just contacted by a research group formed by Ben Adida at Harvard University, Adam Barth at Berkeley University and Collin Jackson at Stanford University. They alerted us of a security issue concerning the Passpack It! button (aka 1Click Login bookmarklet). We fixed it immediately. How the issue was discovered &#8212; The three researchers [...]]]></description>
			<content:encoded><![CDATA[<p>We were just contacted by a research group formed by <a title="Ben Adida" href="http://ben.adida.net" target="_blank">Ben Adida</a> at Harvard University, <a title="Adam Barth" href="http://www.adambarth.com/" target="_blank">Adam Barth</a> at Berkeley University and <a title="Collin Jackson" href="http://www.collinjackson.com/" target="_blank">Collin Jackson</a> at Stanford University. They alerted us of a security issue concerning the <em>Passpack It!</em> button (aka 1Click Login bookmarklet). We fixed it immediately.</p>
<p><strong>How the issue was discovered</strong> &#8212; The three researchers mentioned above are preparing an in-depth study on bookmarklets. The <em>Passpack It!</em> button is one of them. We were able to quickly fix this thanks to the open collaboration of the research group.</p>
<p><strong>Technical description</strong> &#8212; When building 1 Click Login process, we noticed that some sites were arriving back to the server without the referring URL information. To avoid having to refuse 1 Click Login access, the button gathered the originating URL information (saved as an encrypted token) as well as the referring URL in the page header. In the event the referring URL was missing, the URL gathered by the button was used instead by the server in deciding which encrypted login information to reply with. The researchers therefore intentionally suppressed the referring URL header, and redefined a Javascript method in the URL collection process to manipulate the URL information collected by the button.</p>
<p><strong>An example in Layman&#8217;s terms</strong> &#8212; Jack opens his Passpack account and turns on 1 Click Login. Jack starts browsing the internet and happens upon a malicious website built to fool him into pressing his <em>Passpack It!</em> button. Jack falls for it and presses his button. The malicious site then pretends to be, for example, delicious. If Jack has an entry saved in his pack for delicious, the site would be able to retrieve the login credentials for delicious.</p>
<p><strong>The scope of the problem</strong> &#8212; The malicious site needs to include code written specifically for the Passpack 1 Click Login, generic code would not work. Additionally, Jack must be effectively fooled into clicking his button when visiting the site. This may be achieved by typical phishing techniques where the malicious site has copy-catted another well-known site. Jack must both have an entry for the copycatted site in his account <em>and </em>have 1 Click Login activated in that exact moment.</p>
<p><strong>What we did to fix this</strong> &#8212; We now strictly enforce that server only responds to calls from the 1 Click Login button that are accompanied by a referring URL.</p>
<p><strong>What it means for you </strong>&#8211; This will cause sites that repress the referring URL to not work with 1 Click Login.</p>
<p>Thanks Adam, Ben and Collin!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.passpack.com/2008/10/reinstall-1click-login-button/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
