<?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: Common Password Salting</title>
	<atom:link href="http://blog.stevex.net/2006/02/common-password-salting/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.stevex.net/2006/02/common-password-salting/</link>
	<description>Software development and other notes.</description>
	<lastBuildDate>Fri, 03 Feb 2012 14:03:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Marty Combs</title>
		<link>http://blog.stevex.net/2006/02/common-password-salting/comment-page-1/#comment-219971</link>
		<dc:creator>Marty Combs</dc:creator>
		<pubDate>Wed, 07 Nov 2007 01:26:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.stevex.net/index.php/2006/02/17/common-password-salting/#comment-219971</guid>
		<description>This is sometimes tricky to implement as password requirements can vary drastically from site to site.  One site may not allow anything outside alphanumeric characters while another requires some form of punctuation.  I have even come across some that want either a maximum number of characters or an exact number of characters in length (sad but true).</description>
		<content:encoded><![CDATA[<p>This is sometimes tricky to implement as password requirements can vary drastically from site to site.  One site may not allow anything outside alphanumeric characters while another requires some form of punctuation.  I have even come across some that want either a maximum number of characters or an exact number of characters in length (sad but true).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Atul M. Kulkarni</title>
		<link>http://blog.stevex.net/2006/02/common-password-salting/comment-page-1/#comment-124832</link>
		<dc:creator>Atul M. Kulkarni</dc:creator>
		<pubDate>Tue, 05 Jun 2007 08:52:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.stevex.net/index.php/2006/02/17/common-password-salting/#comment-124832</guid>
		<description>This is very useful information for any web user, it is very safe and secure to use these tricks for user names and passwords. Definitely it will help to keep u r accounts safe and secure.</description>
		<content:encoded><![CDATA[<p>This is very useful information for any web user, it is very safe and secure to use these tricks for user names and passwords. Definitely it will help to keep u r accounts safe and secure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Al Sutton</title>
		<link>http://blog.stevex.net/2006/02/common-password-salting/comment-page-1/#comment-14684</link>
		<dc:creator>Al Sutton</dc:creator>
		<pubDate>Thu, 14 Sep 2006 06:33:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.stevex.net/index.php/2006/02/17/common-password-salting/#comment-14684</guid>
		<description>The problem of loosing the database is a good point, but when you&#039;re working in companies where any one of a number of techies could change the password then you get into trouble because your salting method will be different from the next guys, and that&#039;s where problems start.

I&#039;ve been working on a multi-user web based password safe which means theres only one database to backup/replicate for all of the IT department, and from the number of companies purchasing it I&#039;d guess it&#039;s the way things will go. 

btw, if you&#039;re interested the product is at http://www.argosytelcrest.com/eps.html</description>
		<content:encoded><![CDATA[<p>The problem of loosing the database is a good point, but when you&#8217;re working in companies where any one of a number of techies could change the password then you get into trouble because your salting method will be different from the next guys, and that&#8217;s where problems start.</p>
<p>I&#8217;ve been working on a multi-user web based password safe which means theres only one database to backup/replicate for all of the IT department, and from the number of companies purchasing it I&#8217;d guess it&#8217;s the way things will go. </p>
<p>btw, if you&#8217;re interested the product is at <a href="http://www.argosytelcrest.com/eps.html" rel="nofollow">http://www.argosytelcrest.com/eps.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Koda</title>
		<link>http://blog.stevex.net/2006/02/common-password-salting/comment-page-1/#comment-637</link>
		<dc:creator>Koda</dc:creator>
		<pubDate>Mon, 20 Feb 2006 06:13:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.stevex.net/index.php/2006/02/17/common-password-salting/#comment-637</guid>
		<description>&lt;strong&gt;Internet Smarts: Password Salting...&lt;/strong&gt;

	Do you use salted passwords? Or are you currently asking yourself if you have heard the term before? 
	If so, do yourself (and your identity) a favor and take a look at SteveX&#8217;s &#8220;Common Password Salting,&#8221; a nice, succinct writeup on ...</description>
		<content:encoded><![CDATA[<p><strong>Internet Smarts: Password Salting&#8230;</strong></p>
<p>	Do you use salted passwords? Or are you currently asking yourself if you have heard the term before?<br />
	If so, do yourself (and your identity) a favor and take a look at SteveX&#8217;s &#8220;Common Password Salting,&#8221; a nice, succinct writeup on &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chromakode</title>
		<link>http://blog.stevex.net/2006/02/common-password-salting/comment-page-1/#comment-636</link>
		<dc:creator>Chromakode</dc:creator>
		<pubDate>Mon, 20 Feb 2006 05:58:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.stevex.net/index.php/2006/02/17/common-password-salting/#comment-636</guid>
		<description>Well written and very good advice. I was not aware of the emergent problem of such password-abusing social networking sites, though the trick has been around for a long time! Salting is an excellent security practice, and really should become a part of common Internet safety. You give a good suggestion to choose letters at certain indexes, though I would suggest going a bit further, with more (4-5) unique letters in the password. That way, if one guesses the use of a salt, they will have a much harder time at cracking it. Nice post, I&#039;ll be linking to it in my own blog. :)</description>
		<content:encoded><![CDATA[<p>Well written and very good advice. I was not aware of the emergent problem of such password-abusing social networking sites, though the trick has been around for a long time! Salting is an excellent security practice, and really should become a part of common Internet safety. You give a good suggestion to choose letters at certain indexes, though I would suggest going a bit further, with more (4-5) unique letters in the password. That way, if one guesses the use of a salt, they will have a much harder time at cracking it. Nice post, I&#8217;ll be linking to it in my own blog. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stevex</title>
		<link>http://blog.stevex.net/2006/02/common-password-salting/comment-page-1/#comment-633</link>
		<dc:creator>stevex</dc:creator>
		<pubDate>Sun, 19 Feb 2006 13:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.stevex.net/index.php/2006/02/17/common-password-salting/#comment-633</guid>
		<description>The reason I don&#039;t like programs like that is if I lose my password database, I&#039;ve lost access to everything.  Plus, it means that all your passwords are stored on your computer, so if someone breaks into your network (or steals your computer), you&#039;re completely vulnerable.  With this sort of salting algorithm, the password is in my head, yet it&#039;s still unique for every site.</description>
		<content:encoded><![CDATA[<p>The reason I don&#8217;t like programs like that is if I lose my password database, I&#8217;ve lost access to everything.  Plus, it means that all your passwords are stored on your computer, so if someone breaks into your network (or steals your computer), you&#8217;re completely vulnerable.  With this sort of salting algorithm, the password is in my head, yet it&#8217;s still unique for every site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George V. Reilly</title>
		<link>http://blog.stevex.net/2006/02/common-password-salting/comment-page-1/#comment-632</link>
		<dc:creator>George V. Reilly</dc:creator>
		<pubDate>Sun, 19 Feb 2006 04:09:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.stevex.net/index.php/2006/02/17/common-password-salting/#comment-632</guid>
		<description>Good advice.

What I do, however, is to use a password manager program, which generates distinct strong passwords for each website and remembers them for me. I like KeePass, http://keepass.sf.net, but there are a number of such programs out there.</description>
		<content:encoded><![CDATA[<p>Good advice.</p>
<p>What I do, however, is to use a password manager program, which generates distinct strong passwords for each website and remembers them for me. I like KeePass, <a href="http://keepass.sf.net" rel="nofollow">http://keepass.sf.net</a>, but there are a number of such programs out there.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

