<?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: Do sweat the small stuff</title>
	<atom:link href="http://www.pathf.com/blogs/2007/10/do-sweat-the-sm/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2007/10/do-sweat-the-sm/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Mon, 01 Dec 2008 23:48:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Weex</title>
		<link>http://www.pathf.com/blogs/2007/10/do-sweat-the-sm/#comment-280</link>
		<dc:creator>Weex</dc:creator>
		<pubDate>Tue, 09 Oct 2007 16:58:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=230#comment-280</guid>
		<description>&lt;p&gt;You could just show smth like:&lt;br /&gt;
"If the email address is valid then an e-mail has been sent to this email address with information on how to restore your password."&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>You could just show smth like:<br />
&#8220;If the email address is valid then an e-mail has been sent to this email address with information on how to restore your password.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Levitt</title>
		<link>http://www.pathf.com/blogs/2007/10/do-sweat-the-sm/#comment-279</link>
		<dc:creator>Jay Levitt</dc:creator>
		<pubDate>Tue, 09 Oct 2007 00:32:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=230#comment-279</guid>
		<description>&lt;p&gt;Until about two weeks ago, I also believed that a login form was more secure if it didn't tell you *which* field was invalid.  After all, why give a potential hacker more information than they need?&lt;/p&gt;

&lt;p&gt;Then I read a blog entry that pointed out what, in retrospect, should have been blindingly obvious: If a hacker wants to know whether the username is valid, all they have to do is click the "Forgot password?" link.  Most sites will tell you either "we sent a reminder/reset" or "we don't know who that is".  And the alternative - don't even give feedback about whether you've sent off an e-mail - is horrid.&lt;/p&gt;

&lt;p&gt;So, yeah, go ahead and tell people which field they need to fix.  It's OK.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Until about two weeks ago, I also believed that a login form was more secure if it didn&#8217;t tell you *which* field was invalid.  After all, why give a potential hacker more information than they need?</p>
<p>Then I read a blog entry that pointed out what, in retrospect, should have been blindingly obvious: If a hacker wants to know whether the username is valid, all they have to do is click the &#8220;Forgot password?&#8221; link.  Most sites will tell you either &#8220;we sent a reminder/reset&#8221; or &#8220;we don&#8217;t know who that is&#8221;.  And the alternative - don&#8217;t even give feedback about whether you&#8217;ve sent off an e-mail - is horrid.</p>
<p>So, yeah, go ahead and tell people which field they need to fix.  It&#8217;s OK.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keeto</title>
		<link>http://www.pathf.com/blogs/2007/10/do-sweat-the-sm/#comment-278</link>
		<dc:creator>Keeto</dc:creator>
		<pubDate>Mon, 08 Oct 2007 21:06:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=230#comment-278</guid>
		<description>&lt;p&gt;I agree with much of the things you said. Being a webapp developer myself, I often find myself wanting to download and run my own copies of many web applications, simply because I want to change little things that are too annoying for me..&lt;/p&gt;

&lt;p&gt;But with regards to login forms, I guess many application developers still feel the need to be vague. One point that always sticks out whenever discussing user feedback with logins is how much information to share with the users regarding the authentication process.&lt;/p&gt;

&lt;p&gt;It does make sense. If you give only a foggy hint regarding the authentication, you increase the amount of time potential hackers need to break it. The more information you share, the lesser the hackers have to work.&lt;/p&gt;

&lt;p&gt;Of course, it doesn't follow that being vague secures you application more. Security, after all, isn't just limited to basic authentication. But many have been taught that this method helps, and I guess that's why it sticks..&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I agree with much of the things you said. Being a webapp developer myself, I often find myself wanting to download and run my own copies of many web applications, simply because I want to change little things that are too annoying for me..</p>
<p>But with regards to login forms, I guess many application developers still feel the need to be vague. One point that always sticks out whenever discussing user feedback with logins is how much information to share with the users regarding the authentication process.</p>
<p>It does make sense. If you give only a foggy hint regarding the authentication, you increase the amount of time potential hackers need to break it. The more information you share, the lesser the hackers have to work.</p>
<p>Of course, it doesn&#8217;t follow that being vague secures you application more. Security, after all, isn&#8217;t just limited to basic authentication. But many have been taught that this method helps, and I guess that&#8217;s why it sticks..</p>
]]></content:encoded>
	</item>
</channel>
</rss>
