<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Forgot Your Password?</title><link>http://blogs.msdn.com/b/dtjones/archive/2011/06/06/forgot-your-password.aspx</link><description>I’ve seen three basic patterns for handling forgotten web site passwords: Send a change password link to the email address on file Ask one or more challenge questions (or personal information) to unlock the change password screen Send the password, in</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Forgot Your Password?</title><link>http://blogs.msdn.com/b/dtjones/archive/2011/06/06/forgot-your-password.aspx#10171925</link><pubDate>Tue, 07 Jun 2011 04:39:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:10171925</guid><dc:creator>Henry Boehlert</dc:creator><description>&lt;p&gt;Look at the options frameworks such as the ASP.NET membership provider offer to somebody not wanting to spend too much time on implementing authentication.&lt;/p&gt;
&lt;p&gt;It&amp;#39;ll come down to salted hashed passwords and randomly generated (initial) passwords sent by email.&lt;/p&gt;
&lt;p&gt;AFAIK with ASP.NET, change password links are more effort.&lt;/p&gt;
&lt;p&gt;Anyway, we&amp;#39;ll all go OAuth or Facebook, sooner or later.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=10171925" width="1" height="1"&gt;</description></item></channel></rss>