<?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: Password paradox</title>
	<atom:link href="http://www.dancingmango.com/blog/2006/07/12/password-paradox/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dancingmango.com/blog/2006/07/12/password-paradox/</link>
	<description>For more than a decade Marc has been a passionate advocate of placing the customer at the heart of business, working with clients in finance, retail, government and entertainment sectors, helping them craft compelling cross channel customer experiences.  Marc champions lean and agile approaches for making customer driven innovation happen.  He brings design thinking and creativity to clients, engaging across the organisation with a focus on delivery as well as ideas.  He is currently writing a book on Agile Experience Design to be published this Autumn.</description>
	<lastBuildDate>Sun, 25 Sep 2011 23:33:07 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Richard Schwartz</title>
		<link>http://www.dancingmango.com/blog/2006/07/12/password-paradox/comment-page-1/#comment-1649</link>
		<dc:creator>Richard Schwartz</dc:creator>
		<pubDate>Wed, 12 Jul 2006 17:59:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.dancingmango.com/blog/?p=61#comment-1649</guid>
		<description>You are entitled to think whatever you want about Lotus Notes, call it dreadful, etc. -- but please be aware that this is not the default behavior of the product.  This was a choice made by the Notes administrators in your own organization.  They have bought into the (foolish, IMHO) conventional wisdom that requiring frequent password changes and  dis-allowing re-use improves security because it guarantees that any hole opened up will be closed within a short period of time.  Lotus Notes allows this choice in order to accomodate the people who believe this, along with various other options for managing passwords -- including requiring no changes at all, ever.  I have had the same password for Lotus Notes for 13 years now.  Of course, it helps that I am the administrator, so I set the policies.  So anyhow in this case your argument is really with your own company&#039;s policies, not with the product.

-rhs</description>
		<content:encoded><![CDATA[<p>You are entitled to think whatever you want about Lotus Notes, call it dreadful, etc. &#8212; but please be aware that this is not the default behavior of the product.  This was a choice made by the Notes administrators in your own organization.  They have bought into the (foolish, IMHO) conventional wisdom that requiring frequent password changes and  dis-allowing re-use improves security because it guarantees that any hole opened up will be closed within a short period of time.  Lotus Notes allows this choice in order to accomodate the people who believe this, along with various other options for managing passwords &#8212; including requiring no changes at all, ever.  I have had the same password for Lotus Notes for 13 years now.  Of course, it helps that I am the administrator, so I set the policies.  So anyhow in this case your argument is really with your own company&#8217;s policies, not with the product.</p>
<p>-rhs</p>
]]></content:encoded>
	</item>
</channel>
</rss>

