Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 82592 invoked by uid 500); 20 Sep 2001 20:54:12 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 82581 invoked by uid 500); 20 Sep 2001 20:54:12 -0000 Delivered-To: apmail-new-httpd@apache.org From: "Mladen Turk" To: "sterling" , Subject: RE: [ENHANCEMENT] htpasswd utility with DBM support Date: Thu, 20 Sep 2001 23:00:44 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ns.promo-grupa.com X-AntiAbuse: Original Domain - apache.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0] X-AntiAbuse: Sender Address Domain - mappingsoft.com X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I'm currently working on some kind of a 'generalized' htpasswd utility. It is a complete rewrite of htpasswd, that will be easily expanded through modules. There has been some suggestions to keep the htpasswd as small as possible, and make something like htdbm. Don't know if that is the right way through but I'll post the new htpasswd and wait for comments. > -----Original Message----- > From: sterling [mailto:sterling@covalent.net] > Sent: Thursday, September 20, 2001 8:50 PM > To: new-httpd@apache.org > Cc: Mladen Turk > Subject: Re: [ENHANCEMENT] htpasswd utility with DBM support > > > Did this get dropped?? > > I believe this functionality is a requirement. If anyone wants to use > auth_dbm with apr_dbm, there is currently no reliable way to generate the > userdatabase for the dbm their apr is built with without writing c code. > > This patch *does* work, though I agree with wrowe's assessment. Anyone > have the time to do it right? > > > sterling > > > On Tue, 21 Aug 2001, William A. Rowe, > Jr. wrote: > > > From: "William A. Rowe, Jr." > > Sent: Tuesday, August 14, 2001 2:40 PM > > > > > > > From: "Mladen Turk" > > > Sent: Monday, August 13, 2001 6:21 AM > > > > > > > > > > Here is an enhancement that enables username management > using either SDBM or > > > > any other apr supported DBM. I've tested it only using SDBM > on WIN32, but it > > > > should compile on other platforms. > > > > > > > > I know that there is a dbmmanage.pl perl script that is > used to manage DBM > > > > files, but since apr supports dbm, here is the solution. > > > > > > +1 > > > > ... in theory. However, please look at dbmmanage.pl again. > Unfortuantely, this > > patch appears to wipe out any changes to the user's groups or > comments, and certainly > > doesn't allow the user to manipulate those. > > > > If you don't mind submitting an dbmusers.c that rolls in these > features, I would > > definately be willing to consider droping the .pl script. I'd > really prefer we stay > > with the dbmmanage syntax, and ultimately add some syntax to > choose the dbm type, > > if anyone gets to rolling that in apr-util and mod_auth_dbm. > [Then, we can finally > > _delete_ mod_auth_db, presuming all the features have been > rolled into mod_auth_dbm.] > > > > > > > > >