<?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 problems with crypt() and htpasswd files</title>
	<atom:link href="http://paul-m-jones.com/archives/134/feed" rel="self" type="application/rss+xml" />
	<link>http://paul-m-jones.com/archives/134?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=password-problems-with-crypt-and-htpasswd-files</link>
	<description>It&#039;s not enough to be smart; you have to actually know things.</description>
	<lastBuildDate>Wed, 16 May 2012 17:27:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Sami</title>
		<link>http://paul-m-jones.com/archives/134/comment-page-1#comment-419969</link>
		<dc:creator>Sami</dc:creator>
		<pubDate>Fri, 18 Mar 2011 08:55:30 +0000</pubDate>
		<guid isPermaLink="false">http://paul-m-jones.com/blog/?p=134#comment-419969</guid>
		<description>I found that out too, with the latest stable Debian release. I wonder how this kind of problem is still here, after 6 years from the original post of this thread.</description>
		<content:encoded><![CDATA[<p>I found that out too, with the latest stable Debian release. I wonder how this kind of problem is still here, after 6 years from the original post of this thread.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul M. Jones &#187; Blog Archive &#187; Htpasswd and crypt() in Solar &#8212; fixed!</title>
		<link>http://paul-m-jones.com/archives/134/comment-page-1#comment-160852</link>
		<dc:creator>Paul M. Jones &#187; Blog Archive &#187; Htpasswd and crypt() in Solar &#8212; fixed!</dc:creator>
		<pubDate>Thu, 12 Jul 2007 01:55:14 +0000</pubDate>
		<guid isPermaLink="false">http://paul-m-jones.com/blog/?p=134#comment-160852</guid>
		<description>[...] Paul M. Jones If it&#8217;s worth doing, it&#8217;s worth over-doing.      &#171; Password problems with crypt() and htpasswd files  Solar 0.1.0 Released &#187; [...]</description>
		<content:encoded><![CDATA[<p>[...] Paul M. Jones If it&#8217;s worth doing, it&#8217;s worth over-doing.      &laquo; Password problems with crypt() and htpasswd files  Solar 0.1.0 Released &raquo; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Liam</title>
		<link>http://paul-m-jones.com/archives/134/comment-page-1#comment-7329</link>
		<dc:creator>Liam</dc:creator>
		<pubDate>Thu, 28 Apr 2005 00:24:15 +0000</pubDate>
		<guid isPermaLink="false">http://paul-m-jones.com/blog/?p=134#comment-7329</guid>
		<description>This is from the GNU crypt man pages.

GNU EXTENSION
       The glibc2 version of this function has the following  additional  fea-
       tures.	If  salt is a character string starting with the three charac-
       ters &quot;$1$&quot; followed by at most eight characters, and optionally	termi-
       nated  by  &quot;$&quot;,	then instead of using the DES machine, the glibc crypt
       function uses an MD5-based algorithm,  and  outputs  up	to  34	bytes,
       namely  &quot;$1$$&quot;, where &quot;&quot; stands for the up to 8 charac-
       ters following &quot;$1$&quot; in the salt, followed by 22 bytes chosen from  the
       set [a-zA-Z0-9./].  The entire key is significant here (instead of only
       the first 8 bytes).

       Programs using this function must be linked with -lcrypt</description>
		<content:encoded><![CDATA[<p>This is from the GNU crypt man pages.</p>
<p>GNU EXTENSION<br />
       The glibc2 version of this function has the following  additional  fea-<br />
       tures.	If  salt is a character string starting with the three charac-<br />
       ters &#8220;$1$&#8221; followed by at most eight characters, and optionally	termi-<br />
       nated  by  &#8220;$&#8221;,	then instead of using the DES machine, the glibc crypt<br />
       function uses an MD5-based algorithm,  and  outputs  up	to  34	bytes,<br />
       namely  &#8220;$1$$&#8221;, where &#8220;&#8221; stands for the up to 8 charac-<br />
       ters following &#8220;$1$&#8221; in the salt, followed by 22 bytes chosen from  the<br />
       set [a-zA-Z0-9./].  The entire key is significant here (instead of only<br />
       the first 8 bytes).</p>
<p>       Programs using this function must be linked with -lcrypt</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith</title>
		<link>http://paul-m-jones.com/archives/134/comment-page-1#comment-6409</link>
		<dc:creator>Keith</dc:creator>
		<pubDate>Thu, 14 Apr 2005 12:41:13 +0000</pubDate>
		<guid isPermaLink="false">http://paul-m-jones.com/blog/?p=134#comment-6409</guid>
		<description>You can use crypt(), MD5 or SHA for password. All within the same password file too. Why not just force users who have older crypt password to change their password and then save it using MD5.</description>
		<content:encoded><![CDATA[<p>You can use crypt(), MD5 or SHA for password. All within the same password file too. Why not just force users who have older crypt password to change their password and then save it using MD5.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pmjones</title>
		<link>http://paul-m-jones.com/archives/134/comment-page-1#comment-6406</link>
		<dc:creator>pmjones</dc:creator>
		<pubDate>Thu, 14 Apr 2005 11:39:57 +0000</pubDate>
		<guid isPermaLink="false">http://paul-m-jones.com/blog/?p=134#comment-6406</guid>
		<description>Hi, Oscar -- You understood; that does appear to be the case.  Apparently it&#039;s a &quot;known limitation&quot; of crypt().  However, I&#039;m doing a little more research and there may be another workaround (e.g., having htpasswd use SHA encryption, but that&#039;s not the default).</description>
		<content:encoded><![CDATA[<p>Hi, Oscar &#8212; You understood; that does appear to be the case.  Apparently it&#8217;s a &#8220;known limitation&#8221; of crypt().  However, I&#8217;m doing a little more research and there may be another workaround (e.g., having htpasswd use SHA encryption, but that&#8217;s not the default).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oscar merida</title>
		<link>http://paul-m-jones.com/archives/134/comment-page-1#comment-6390</link>
		<dc:creator>oscar merida</dc:creator>
		<pubDate>Thu, 14 Apr 2005 04:27:07 +0000</pubDate>
		<guid isPermaLink="false">http://paul-m-jones.com/blog/?p=134#comment-6390</guid>
		<description>Clarification: are you saying that when crypted with the same salt &quot;password&quot; and &quot;password2&quot; produce the same string (or at least strings with matching first eight characters)? 

Or did I misunderstand?</description>
		<content:encoded><![CDATA[<p>Clarification: are you saying that when crypted with the same salt &#8220;password&#8221; and &#8220;password2&#8243; produce the same string (or at least strings with matching first eight characters)? </p>
<p>Or did I misunderstand?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

