The following reply was made to PR general/5514; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]> To: Nicholas Berry <[EMAIL PROTECTED]> Cc: Apache bugs database <[EMAIL PROTECTED]> Subject: Re: general/5514: htpasswd encryption method with apache 1.3.x differs from apache previous to 1.2 Date: Mon, 27 Dec 1999 14:07:10 -0700 (MST) On Mon, 27 Dec 1999, Nicholas Berry wrote: > Does the htaccess portion of Apache 1.3.9 read the encrypted passwords any > differently than past versions or does it read the encrypted passwords based > on the crypt() library included with BSDI 4.01. > > We were running BSDI 3.1 with Apache 1.1.3, but upgraded to BSDI 4.01 (for > Y2K reasons) and upgraded to Apache 1.3.9 for Name based virtual hosting. > Which upgrade affected the way that the system reads the .htpasswd file? > > Thanks for your help. As I said, it uses your OS's crypt() function. You need to figure out what the old crypt() function returned and what the new one does and why your OS is doing something different. > Nicholas Berry > JPS.Net, a Onemain.com Company > Network Operations Department > Cisco Network Engineer > > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: <apache-bugdb@apache.org>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Sent: Monday, December 27, 1999 6:26 PM > Subject: Re: general/5514: htpasswd encryption method with apache 1.3.x > differs from apache previous to 1.2 > > > > [In order for any reply to be added to the PR database, ] > > [you need to include <[EMAIL PROTECTED]> in the Cc line ] > > [and leave the subject line UNCHANGED. This is not done] > > [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! ] > > > > > > Synopsis: htpasswd encryption method with apache 1.3.x differs from apache > previous to 1.2 > > > > State-Changed-From-To: open-closed > > State-Changed-By: marc > > State-Changed-When: Mon Dec 27 10:26:03 PST 1999 > > State-Changed-Why: > > They are perfectly compatible. Normally, Apache doesn't > > encrypt them itself; your OS's crypt() function does. If you > > change OSes and have a different crypt() function, then... > > well... there isn't much we can do about that... > > > > If I were you, I would look very closely at the problem to > > ensure that what you think is the problem is actually the > > problem and it isn't really something else. > > > > >
