Received: (qmail 11650 invoked by uid 501); 30 May 2001 19:34:12 -0000
Message-Id: <20010530193412.11646.qmail@apache.org>
Date: 30 May 2001 19:34:12 -0000
From: Graham Van Epps <gvanepps@gankish.net>
Reply-To: gvanepps@gankish.net
To: submit@bugz.apache.org
Subject: htpasswd authentication segfaults, as does the htpasswd command.
X-Send-Pr-Version: 3.110

>Number:         7792
>Category:       mod_auth-any
>Synopsis:       htpasswd authentication segfaults, as does the htpasswd command.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed May 30 12:40:00 PDT 2001
>Closed-Date:    Thu May 31 10:20:25 PDT 2001
>Last-Modified:  Thu May 31 10:20:25 PDT 2001
>Originator:     gvanepps@gankish.net
>Release:        1.3.20, 1.3.19
>Organization:
>Environment:
Linux db1 2.2.19 #2 SMP Mon May 28 12:28:02 EDT 2001 i686 unknown
System 1 is a quad proc Xeon with raid, oodles of memory, etc.
System 2 is a dual proc pentium classic 
>Description:
I tried to create a htpasswd file, but the binary segfaults once the password is entered.  It leaves this in the error_log:
[Sun May 27 23:53:52 2001] [notice] child pid 2069 exit signal Segmentation fault (11)
Ive reproduced the problem on two different smp slackware 7.1 boxes running kernel 2.2.19 with apache 1.3.19 and 1.3.20.
>How-To-Repeat:
i think any slack 7.1 system (full install), perhaps multiprocessor will also have the same problem.
>Fix:
could it be a library dependancy that slackware doesnt have or the way the password is encrypted?
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: marc
State-Changed-When: Thu May 31 10:20:24 PDT 2001
State-Changed-Why:
This is due to a bug in Slackware that requires all calls to crypt() to use some magic string in the salt.  This completely violates all standards and will cause nearly every non-slackware-specific piece of code to fail.  

You may be able to work around it by installing the DES crypt option to slackware.  If you dislike the completely non-standard way that Slackware works, you should file a bug report with them.
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]