You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Michael McLagan <Mi...@Linux.ORG> on 1998/07/12 13:27:30 UTC

mod_auth-any/2597: dbmmanage generates incorrect file

>Number:         2597
>Category:       mod_auth-any
>Synopsis:       dbmmanage generates incorrect file
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sun Jul 12 04:30:00 PDT 1998
>Last-Modified:
>Originator:     Michael.McLagan@Linux.ORG
>Organization:
apache
>Release:        1.3
>Environment:
Redhat 5.0, GDBM 1.7.3, Perl v5.004, Linux 2.0.34
>Description:
using dbmmanage generates a file without the .db extension.

When presented with a file with a .db extension, it will not view
the contents.

renaming the file to 'sitepasswd.db' allows it to be accessed by
mod_auth_dbm.
>How-To-Repeat:
dbmmanage sitepasswd adduser mmclagan  <<-- generates 'sitepasswd'
AuthDBMUserFile sitepasswd  <<-- in .htaccess

access something in the directory
>Fix:
modify the perl file so that it uses the extension if given?  rename
the output file to accomodate the missing .db ?

>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]