<?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: Banks like cookies</title>
	<atom:link href="http://habitablezone.com/2012/05/19/banks-like-cookies/feed/" rel="self" type="application/rss+xml" />
	<link>https://habitablezone.com/2012/05/19/banks-like-cookies/</link>
	<description></description>
	<lastBuildDate>Fri, 03 Apr 2026 22:41:18 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Robert</title>
		<link>https://habitablezone.com/2012/05/19/banks-like-cookies/#comment-15182</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Sun, 20 May 2012 18:13:08 +0000</pubDate>
		<guid isPermaLink="false">http://habitablezone.com/?p=15214#comment-15182</guid>
		<description>What bank do you use? What&#039;s your account number and password so I can go check on the problem? he he he he...

Cookies haven&#039;t been the huge issue they used to be, these last few years. People have gotten their heads around distinctions like session cookies versus permanent cookies versus third party cookies, for the most part. But banks seem to push the envelope in pursuit of higher security, and some of the things they try seem to require cookies used in relatively unusual ways.

In one bank scheme I&#039;ve seen, a cookie pre-identifies you when you get to the login page, and in addition to the usual username and password boxes, it&#039;s preloaded an image I chose when I registered. Supposedly the image can&#039;t be counterfeited, and if I recognize it, I&#039;m supposed to be reassured that I&#039;m not at a phishing site, and it&#039;s safe to proceed to log in. Sounds good in concept, since it could prevent you from supplying a password at a phishing site. But if you lose that cookie, the site won&#039;t begin the login process, and somehow you need to reestablish your credentials. It hasn&#039;t happened yet so I don&#039;t know what the procedure is, but it can&#039;t be pretty.

There are a lot of ways to address the problem of authenticating online, but anything beyond supplying a memorized code has the Achilles Heel of requiring you to posses some kind of documentation to identify yourself to a computer. Digital certificates would be far more secure than cookies, but you&#039;d still be SOL if you lose the certificate. In all places at all times, you&#039;re hosed if your papers aren&#039;t in order.</description>
		<content:encoded><![CDATA[<p>What bank do you use? What&#8217;s your account number and password so I can go check on the problem? he he he he&#8230;</p>
<p>Cookies haven&#8217;t been the huge issue they used to be, these last few years. People have gotten their heads around distinctions like session cookies versus permanent cookies versus third party cookies, for the most part. But banks seem to push the envelope in pursuit of higher security, and some of the things they try seem to require cookies used in relatively unusual ways.</p>
<p>In one bank scheme I&#8217;ve seen, a cookie pre-identifies you when you get to the login page, and in addition to the usual username and password boxes, it&#8217;s preloaded an image I chose when I registered. Supposedly the image can&#8217;t be counterfeited, and if I recognize it, I&#8217;m supposed to be reassured that I&#8217;m not at a phishing site, and it&#8217;s safe to proceed to log in. Sounds good in concept, since it could prevent you from supplying a password at a phishing site. But if you lose that cookie, the site won&#8217;t begin the login process, and somehow you need to reestablish your credentials. It hasn&#8217;t happened yet so I don&#8217;t know what the procedure is, but it can&#8217;t be pretty.</p>
<p>There are a lot of ways to address the problem of authenticating online, but anything beyond supplying a memorized code has the Achilles Heel of requiring you to posses some kind of documentation to identify yourself to a computer. Digital certificates would be far more secure than cookies, but you&#8217;d still be SOL if you lose the certificate. In all places at all times, you&#8217;re hosed if your papers aren&#8217;t in order.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
