Received: (qmail 29225 invoked by uid 2012); 31 Dec 1999 23:34:28 -0000 Message-Id: <19991231233428.29224.qmail@hyperreal.org> Date: 31 Dec 1999 23:34:28 -0000 From: Philip Wall Reply-To: wallp@earthlink.net To: apbugs@hyperreal.org Subject: dbmmanage no longer supports groups X-Send-Pr-Version: 3.2 >Number: 5527 >Category: mod_auth-any >Synopsis: dbmmanage no longer supports groups >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Fri Dec 31 15:40:01 PST 1999 >Closed-Date: Wed Sep 20 13:08:17 PDT 2000 >Last-Modified: Wed Sep 20 13:08:17 PDT 2000 >Originator: wallp@earthlink.net >Release: 1.3.9 >Organization: >Environment: Linux 2.2.13 >Description: The earlier versions of dbmmanage, atleast the ones that came with 1.2.x supported adding group fields to the db files it generated via the adduser command. The adduser command also used to run straight from the command line and didn't prompt for a password. Is it possible to get the old functionality back or atleast the group field part? Apacheweek originally posted the the group stuff in their How to Use DBM auth article. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: wrowe State-Changed-When: Wed Sep 20 13:08:17 PDT 2000 State-Changed-Why: This feature is (re)implemented in Apache 1.3.13 and 2.0 >Unformatted: [In order for any reply to be added to the PR database, you need] [to include 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! ]