<?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: Passwords</title>
	<atom:link href="http://www.bitsbook.com/2008/09/passwords/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bitsbook.com/2008/09/passwords/</link>
	<description>Your Life, Liberty and Happiness After the Digital Explosion</description>
	<pubDate>Wed, 07 Jan 2009 03:47:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Writing Secure Code - Links - September 26, 2008 &#124; Programmer's Edge</title>
		<link>http://www.bitsbook.com/2008/09/passwords/#comment-856</link>
		<dc:creator>Writing Secure Code - Links - September 26, 2008 &#124; Programmer's Edge</dc:creator>
		<pubDate>Tue, 30 Sep 2008 15:01:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitsbook.com/?p=200#comment-856</guid>
		<description>[...] Passwords &#8212; This blog post from the &#34;Blown to Bits&#34; blog talks about problems with passwords. On a personal level - you should have a random password. No words. Just mix of characters. From a developer perspective - do not write your own login code. Almost all frameworks now have their own login subsystem - leverage that. It will allow you to focus on code that is actually core to your business application. Or as I would think - I would not want my friend Quan writing my UI but he knows how to write awesome security code. I know my friend Josh knows how to make awesome looking UI - he shouldn&#8217;t be writing my security code. And from an enterprise level - make sure you are adopting&#160; comprehensive access products such as Oracle Access Manager suite. [...]</description>
		<content:encoded><![CDATA[<p>[...] Passwords &#8212; This blog post from the &quot;Blown to Bits&quot; blog talks about problems with passwords. On a personal level - you should have a random password. No words. Just mix of characters. From a developer perspective - do not write your own login code. Almost all frameworks now have their own login subsystem - leverage that. It will allow you to focus on code that is actually core to your business application. Or as I would think - I would not want my friend Quan writing my UI but he knows how to write awesome security code. I know my friend Josh knows how to make awesome looking UI - he shouldn&#8217;t be writing my security code. And from an enterprise level - make sure you are adopting&#160; comprehensive access products such as Oracle Access Manager suite. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blown to Bits &#187; Blog Archive &#187; Sarah Palin&#8217;s Email</title>
		<link>http://www.bitsbook.com/2008/09/passwords/#comment-706</link>
		<dc:creator>Blown to Bits &#187; Blog Archive &#187; Sarah Palin&#8217;s Email</dc:creator>
		<pubDate>Thu, 18 Sep 2008 13:30:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitsbook.com/?p=200#comment-706</guid>
		<description>[...] Passwords  [...]</description>
		<content:encoded><![CDATA[<p>[...] Passwords  [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
