Return-Path: <new-httpd-owner-new-httpd-archive=hyperreal.org@apache.org>
Delivered-To: new-httpd-archive@hyperreal.org
Received: (qmail 26123 invoked by uid 6000); 18 Mar 1999 00:32:55 -0000
Received: (qmail 26026 invoked from network); 18 Mar 1999 00:32:51 -0000
Received: from smtp8.teleport.com (192.108.254.52)
  by taz.hyperreal.org with SMTP; 18 Mar 1999 00:32:51 -0000
Received: (qmail 2804 invoked from network); 18 Mar 1999 00:32:50 -0000
Received: from user2.teleport.com (reliant@192.108.254.12)
  by smtp8.teleport.com with SMTP; 18 Mar 1999 00:32:50 -0000
Received: (from reliant@localhost)
          by user2.teleport.com (8.8.7/8.8.4)
	  id QAA13436 for new-httpd@apache.org; Wed, 17 Mar 1999 16:32:49 -0800 (PST)
Date: Wed, 17 Mar 1999 16:32:49 -0800 (PST)
Message-Id: <199903180032.QAA13436@user2.teleport.com>
To: new-httpd@apache.org
Subject: Re: encrypting passwords
From: "Charles Sliger" <chaz@reliant.com>
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

I could use htpasswd in a perl script on the server to do this
that is true.  I would prefer to have a way to perform the
encryption on the client side and not pass the password accross
the net cleartext.
-chaz


From: Chris Ewert <radio_1@geocities.com>
the htpasswd tool could be used to do that.  Its a support program
included in the distribution.  I assume that you are talking about a
.htpasswd file.


Charles Sliger wrote:
> How do I encrypt a password such that the Apache server
> will understand it?
> I can't seem to find documentation discussing such things
> as the seed used.
> -chaz