>Number: 4695
>Category: general
>Synopsis: Bad behavior of dbmmanage "check"
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Mon Jul 5 06:40:00 PDT 1999
>Last-Modified:
>Originator: [EMAIL PROTECTED]
>Organization:
apache
>Release: 1.3.4
>Environment:
Linux, but should occur anywhere.
>Description:
The "check" command in my version of dbmmanage seems to assume that the
values in the DBM file are merely the crypted passwords. This can be wrong;
a value may look like
<crypted_password>[:<group_list>[:<any_other_stuff>]]
I tried with a user file which contains all of the three possible fields,
and the check command always replies with "password mismatch".
>How-To-Repeat:
Try dbmmanage "check" on any DBM file which combines user and group information.
>Fix:
In dbmc::check(), use split() to extract the crypted password from $DB{$key}.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <[EMAIL PROTECTED]> 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! ]
