Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 20524 invoked by uid 6000); 18 Mar 1999 01:52:04 -0000 Received: (qmail 20396 invoked by uid 24); 18 Mar 1999 01:51:59 -0000 Received: (qmail 20815 invoked from network); 18 Mar 1999 01:07:37 -0000 Received: from crusader.mjhb.marina-del-rey.ca.us (204.254.69.20) by taz.hyperreal.org with SMTP; 18 Mar 1999 01:07:37 -0000 Received: (from marty@localhost) by crusader.mjhb.marina-del-rey.ca.us (8.9.1-MJHB/8.9.1) id RAA02140 for new-httpd@apache.org; Wed, 17 Mar 1999 17:07:32 -0800 (PST) (envelope-from marty) Message-ID: <19990317170732.A2107@crusader.mjhb.marina-del-rey.ca.us> Date: Wed, 17 Mar 1999 17:07:32 -0800 From: Marty Bower To: new-httpd@apache.org Subject: Re: encrypting passwords References: <199903180054.QAA18218@user2.teleport.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903180054.QAA18218@user2.teleport.com>; from Charles Sliger on Wed, Mar 17, 1999 at 04:54:25PM -0800 Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org On Wed, Mar 17, 1999 at 04:54:25PM -0800, Charles Sliger wrote: > On the server, how would I programatically encrypt the > password? htpasswd seems to require interaction. The encryption is performed in the add_password() routine in htpasswd.c, and relies on the crypt() function provided by the operating system. You could fairly easily customize htpasswd to do whatever it is that you want to do, or graft the guts of add_password() into your own creation. -- Marty Bower | http://mjhb.marina-del-rey.ca.us | marty@mjhb.mdr.ca.us