<?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: Forced password change</title>
	<atom:link href="http://blog.cluepusher.dk/2007/09/17/forced-password-change/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.cluepusher.dk/2007/09/17/forced-password-change/</link>
	<description>Diary and thoughtspace of Rune B. Broberg</description>
	<lastBuildDate>Wed, 26 May 2010 16:29:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: femme</title>
		<link>http://blog.cluepusher.dk/2007/09/17/forced-password-change/comment-page-1/#comment-9591</link>
		<dc:creator>femme</dc:creator>
		<pubDate>Tue, 22 Dec 2009 22:40:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cluepusher.dk/2007/09/17/forced-password-change/#comment-9591</guid>
		<description>It&#039;s plain stupid and ignorant to tell someone that the password they have chosen for there own isn&#039;t good enough for you any longer.

It seems to me that the only reason someone would tell a user that they must change their password  is because the company, organization or whatever has had their files hacked and passwords of users were or possible were, compromised because of the company/organization&#039;s lack of proper security and contorl over they system they run/service.</description>
		<content:encoded><![CDATA[<p>It&#8217;s plain stupid and ignorant to tell someone that the password they have chosen for there own isn&#8217;t good enough for you any longer.</p>
<p>It seems to me that the only reason someone would tell a user that they must change their password  is because the company, organization or whatever has had their files hacked and passwords of users were or possible were, compromised because of the company/organization&#8217;s lack of proper security and contorl over they system they run/service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: radiac</title>
		<link>http://blog.cluepusher.dk/2007/09/17/forced-password-change/comment-page-1/#comment-76</link>
		<dc:creator>radiac</dc:creator>
		<pubDate>Wed, 19 Sep 2007 08:02:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cluepusher.dk/2007/09/17/forced-password-change/#comment-76</guid>
		<description>People never read e-mails properly. I regularly send people password-protected URLs, with the username and password directly underneath the URL. I would say 90% of the time I get an e-mail back saying &quot;but it&#039;s asking me for a username and password&quot;...

And I know it&#039;s considered good practice to force password changes, but I&#039;m not convinced:
- if a password is a secret, then its efficacy does not deteriorate with time
- if the secrecy of a password can be broken after the lifetime of the password, then it can be broken within the lifetime of the password
- if a password is no longer a secret, then the new one will escape in the same way as before

For forced password changes to be effective, passwords would need to be changed at every login or every day to mitigate the risks, but that is impractical.

Furthermore, users get to know their passwords. Change it and they&#039;ll have a hard time remembering the new one - they therefore either write it down (reducing secrecy), or make their new password a minor variant of the previous (leaving it easy to guess), effectively negating the purpose of changing passwords. Or worse, they attempt to memorise it, fail, and then have to keep contacting you to get it changed.

Passwords are flawed, and forcing them to be changed skims over the true issues and just introduces new problems. If the account is worth protecting, use two-factor authentication; otherwise enforce strong passwords, take steps to defend against brute force and dictionary attacks, make users aware of the dangers, and take no further responsibility for account security.

Wow, I wrote an essay! Does any of that make sense, or have I overlooked something obvious?</description>
		<content:encoded><![CDATA[<p>People never read e-mails properly. I regularly send people password-protected URLs, with the username and password directly underneath the URL. I would say 90% of the time I get an e-mail back saying &#8220;but it&#8217;s asking me for a username and password&#8221;&#8230;</p>
<p>And I know it&#8217;s considered good practice to force password changes, but I&#8217;m not convinced:<br />
- if a password is a secret, then its efficacy does not deteriorate with time<br />
- if the secrecy of a password can be broken after the lifetime of the password, then it can be broken within the lifetime of the password<br />
- if a password is no longer a secret, then the new one will escape in the same way as before</p>
<p>For forced password changes to be effective, passwords would need to be changed at every login or every day to mitigate the risks, but that is impractical.</p>
<p>Furthermore, users get to know their passwords. Change it and they&#8217;ll have a hard time remembering the new one &#8211; they therefore either write it down (reducing secrecy), or make their new password a minor variant of the previous (leaving it easy to guess), effectively negating the purpose of changing passwords. Or worse, they attempt to memorise it, fail, and then have to keep contacting you to get it changed.</p>
<p>Passwords are flawed, and forcing them to be changed skims over the true issues and just introduces new problems. If the account is worth protecting, use two-factor authentication; otherwise enforce strong passwords, take steps to defend against brute force and dictionary attacks, make users aware of the dangers, and take no further responsibility for account security.</p>
<p>Wow, I wrote an essay! Does any of that make sense, or have I overlooked something obvious?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

