<?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"
	>
<channel>
	<title>Comments on: Turn On Autocomplete</title>
	<atom:link href="http://cafe.elharo.com/web/turn-on-autocomplete/feed/" rel="self" type="application/rss+xml" />
	<link>http://cafe.elharo.com/web/turn-on-autocomplete/</link>
	<description>Longer than a blog; shorter than a book</description>
	<pubDate>Thu, 20 Nov 2008 23:56:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Dentaku</title>
		<link>http://cafe.elharo.com/web/turn-on-autocomplete/#comment-167043</link>
		<dc:creator>Dentaku</dc:creator>
		<pubDate>Wed, 12 Dec 2007 11:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/uncategorized/turn-on-autocomplete/#comment-167043</guid>
		<description>I agree with Hoogla Boogla. The realistic fact is, that most users don't know about the features of browsers. Most havent' heard about cookies or history. They don't understand why sometimes URLs/Names appear in a selection box and sometimes not.

For this reason, security must be defined from the standpoint of "dumb" (sorry...) users. Other users know enough how to configure their software to increase security. Security must be fool proof.

I think of another way to have secure passwords: changing passwords! There would be an algorithm how to create the password with operands oly known to the user. This way, traced passwords/keystrokes are invaluable as those passwords can't be used a second time. It's like a transaction number but with the algorithm and operands being easy enough for the user to remember. E.g. "dayOfWeek * monthOfBirth + 'Hello' "</description>
		<content:encoded><![CDATA[<p>I agree with Hoogla Boogla. The realistic fact is, that most users don&#8217;t know about the features of browsers. Most havent&#8217; heard about cookies or history. They don&#8217;t understand why sometimes URLs/Names appear in a selection box and sometimes not.</p>
<p>For this reason, security must be defined from the standpoint of &#8220;dumb&#8221; (sorry&#8230;) users. Other users know enough how to configure their software to increase security. Security must be fool proof.</p>
<p>I think of another way to have secure passwords: changing passwords! There would be an algorithm how to create the password with operands oly known to the user. This way, traced passwords/keystrokes are invaluable as those passwords can&#8217;t be used a second time. It&#8217;s like a transaction number but with the algorithm and operands being easy enough for the user to remember. E.g. &#8220;dayOfWeek * monthOfBirth + &#8216;Hello&#8217; &#8220;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hoogla Boogla</title>
		<link>http://cafe.elharo.com/web/turn-on-autocomplete/#comment-158210</link>
		<dc:creator>Hoogla Boogla</dc:creator>
		<pubDate>Mon, 19 Nov 2007 14:55:36 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/uncategorized/turn-on-autocomplete/#comment-158210</guid>
		<description>I definitely consider username/password autocomplete a security risk. While you are right, that browsers provide options to clear caches, password stores and the like, most users don't know how to find the right buttons. Even if you have a "this is a public computer"-checkbox, there will be (a lot of) users who are like "oh no, it's not public, it's in my classroom/library/whatever".

Hoogla Boogla</description>
		<content:encoded><![CDATA[<p>I definitely consider username/password autocomplete a security risk. While you are right, that browsers provide options to clear caches, password stores and the like, most users don&#8217;t know how to find the right buttons. Even if you have a &#8220;this is a public computer&#8221;-checkbox, there will be (a lot of) users who are like &#8220;oh no, it&#8217;s not public, it&#8217;s in my classroom/library/whatever&#8221;.</p>
<p>Hoogla Boogla</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gaurav</title>
		<link>http://cafe.elharo.com/web/turn-on-autocomplete/#comment-135169</link>
		<dc:creator>Gaurav</dc:creator>
		<pubDate>Mon, 01 Oct 2007 01:14:21 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/uncategorized/turn-on-autocomplete/#comment-135169</guid>
		<description>I agree that forcing autocomplete off decreases security by forcing users to use fewer passwords. 

I'm reminded of a story by one of the authors (IIRC - Dan Farmer) of Crack (the /etc/passwd brute force cracking program) - the author added the plaintext password file from a MUD site he ran to his dictionary file at a company he was the sysadmin ... on the first pass Crack guessed the root password!

Also some machines e.g IBM/Lenovo Thinkpads are equipped with Fingerprint Readers+Software that fill in login forms (after a simple swipe of the finger) ... even if the HTML requests Autocomplete Off - technically though this isn't Autocomplete as it requires the user to swipe their finger. Also the IBM/Lenovo password manager isn't restricted to only Web Forms - it supports Windows/NTLM, HTTP, VNC and other Login prompts as well.</description>
		<content:encoded><![CDATA[<p>I agree that forcing autocomplete off decreases security by forcing users to use fewer passwords. </p>
<p>I&#8217;m reminded of a story by one of the authors (IIRC - Dan Farmer) of Crack (the /etc/passwd brute force cracking program) - the author added the plaintext password file from a MUD site he ran to his dictionary file at a company he was the sysadmin &#8230; on the first pass Crack guessed the root password!</p>
<p>Also some machines e.g IBM/Lenovo Thinkpads are equipped with Fingerprint Readers+Software that fill in login forms (after a simple swipe of the finger) &#8230; even if the HTML requests Autocomplete Off - technically though this isn&#8217;t Autocomplete as it requires the user to swipe their finger. Also the IBM/Lenovo password manager isn&#8217;t restricted to only Web Forms - it supports Windows/NTLM, HTTP, VNC and other Login prompts as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Orenchak</title>
		<link>http://cafe.elharo.com/web/turn-on-autocomplete/#comment-135090</link>
		<dc:creator>James Orenchak</dc:creator>
		<pubDate>Sun, 30 Sep 2007 15:17:38 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/uncategorized/turn-on-autocomplete/#comment-135090</guid>
		<description>As long as the web site isn't handling transactions, such as Amazon or the home banking web site I use, I see no problem with autocompleting user names and passwords. The trade off is between a hacker stealing the user names and passwords saved by the browser from your pc and someone looking over your shoulder or stealing your user name and password you type in somewhere between the keyboard and the webserver.</description>
		<content:encoded><![CDATA[<p>As long as the web site isn&#8217;t handling transactions, such as Amazon or the home banking web site I use, I see no problem with autocompleting user names and passwords. The trade off is between a hacker stealing the user names and passwords saved by the browser from your pc and someone looking over your shoulder or stealing your user name and password you type in somewhere between the keyboard and the webserver.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Subbu Allamaraju</title>
		<link>http://cafe.elharo.com/web/turn-on-autocomplete/#comment-134515</link>
		<dc:creator>Subbu Allamaraju</dc:creator>
		<pubDate>Fri, 28 Sep 2007 17:42:36 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/uncategorized/turn-on-autocomplete/#comment-134515</guid>
		<description>I agree with your argument that autocomplete is not necessarily a security risk, and it is often a poor choice on the part of web masters and web app developers to disable autocomplete (or to even null-out text fields using JavaScript) assuming that it increases security. It does not.</description>
		<content:encoded><![CDATA[<p>I agree with your argument that autocomplete is not necessarily a security risk, and it is often a poor choice on the part of web masters and web app developers to disable autocomplete (or to even null-out text fields using JavaScript) assuming that it increases security. It does not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Viswanath</title>
		<link>http://cafe.elharo.com/web/turn-on-autocomplete/#comment-134471</link>
		<dc:creator>Viswanath</dc:creator>
		<pubDate>Fri, 28 Sep 2007 16:01:03 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/uncategorized/turn-on-autocomplete/#comment-134471</guid>
		<description>How about the case of forgotten passwords, simply because the browser remembered a ton of them, one for each site, but finally 
 - my PC crashed 
 - new version of the browser didn't faithfully copy
 - I needed to badly access the site from a different PC</description>
		<content:encoded><![CDATA[<p>How about the case of forgotten passwords, simply because the browser remembered a ton of them, one for each site, but finally<br />
 - my PC crashed<br />
 - new version of the browser didn&#8217;t faithfully copy<br />
 - I needed to badly access the site from a different PC</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elliotte Rusty Harold</title>
		<link>http://cafe.elharo.com/web/turn-on-autocomplete/#comment-134369</link>
		<dc:creator>Elliotte Rusty Harold</dc:creator>
		<pubDate>Fri, 28 Sep 2007 10:20:50 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/uncategorized/turn-on-autocomplete/#comment-134369</guid>
		<description>It's a little like trying to push the bubble out of a carpet. You can knock it down one place, but then it shows up somewhere else.

Assuming the browser uses strong encryption and secure coding practices, I'm not too worried about a trojan stealing the file. I am worried that reuse of passwords on multiple sites enables a hacker who gets to one site's often unencrypted password database to then trivially guess the password for different sites. I don't want Joe's Autoshop to have access to my Amazon password. However if I can't store the passwords in the browser, I use many fewer different passwords. These days almost every site or system I connect to has a unique password, but that didn't use to be the case before browsers started autofilling passwords. It was just too much trouble to remember them all.</description>
		<content:encoded><![CDATA[<p>It&#8217;s a little like trying to push the bubble out of a carpet. You can knock it down one place, but then it shows up somewhere else.</p>
<p>Assuming the browser uses strong encryption and secure coding practices, I&#8217;m not too worried about a trojan stealing the file. I am worried that reuse of passwords on multiple sites enables a hacker who gets to one site&#8217;s often unencrypted password database to then trivially guess the password for different sites. I don&#8217;t want Joe&#8217;s Autoshop to have access to my Amazon password. However if I can&#8217;t store the passwords in the browser, I use many fewer different passwords. These days almost every site or system I connect to has a unique password, but that didn&#8217;t use to be the case before browsers started autofilling passwords. It was just too much trouble to remember them all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michaelk</title>
		<link>http://cafe.elharo.com/web/turn-on-autocomplete/#comment-133306</link>
		<dc:creator>Michaelk</dc:creator>
		<pubDate>Tue, 25 Sep 2007 23:55:16 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/uncategorized/turn-on-autocomplete/#comment-133306</guid>
		<description>&#62;That is, autocompleting usernames and passwords definitely increases accessibility and usually increases security.

Yes, it really helps with accessibility, but therein lies a security risk- a virus could be able to get the files containing the autocomplete information, send it to its creator, and then be decrypted.</description>
		<content:encoded><![CDATA[<p>&gt;That is, autocompleting usernames and passwords definitely increases accessibility and usually increases security.</p>
<p>Yes, it really helps with accessibility, but therein lies a security risk- a virus could be able to get the files containing the autocomplete information, send it to its creator, and then be decrypted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FranÃ§ois Beausoleil</title>
		<link>http://cafe.elharo.com/web/turn-on-autocomplete/#comment-133158</link>
		<dc:creator>FranÃ§ois Beausoleil</dc:creator>
		<pubDate>Tue, 25 Sep 2007 15:57:10 +0000</pubDate>
		<guid isPermaLink="false">http://cafe.elharo.com/uncategorized/turn-on-autocomplete/#comment-133158</guid>
		<description>This is nice if you're building a website, but a web application is another matter entirely.  I am specifically talking about admin interfaces, or CRM+ERP built using web interfaces.</description>
		<content:encoded><![CDATA[<p>This is nice if you&#8217;re building a website, but a web application is another matter entirely.  I am specifically talking about admin interfaces, or CRM+ERP built using web interfaces.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
