From nobody@hyperreal.com Wed Dec 4 16:42:56 1996 Received: by taz.hyperreal.com (8.8.3/V2.0) id QAA23109; Wed, 4 Dec 1996 16:42:56 -0800 (PST) Message-Id: <199612050042.QAA23109@taz.hyperreal.com> Date: Wed, 4 Dec 1996 16:42:56 -0800 (PST) From: Dean Ashby Reply-To: ashby@icair.iac.org.nz To: apbugs@hyperreal.com Subject: mod_auth_dbm cannot open dbm file X-Send-Pr-Version: 3.2 >Number: 29 >Category: other >Synopsis: mod_auth_dbm cannot open dbm file >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Wed Dec 4 16:50:00 1996 >Last-Modified: Sat Feb 15 20:50:21 PST 1997 >Originator: ashby@icair.iac.org.nz >Organization: >Release: 1.2b1 >Environment: Sun SPARCstation 20 Solaris 2.4 gcc 2.7.2 >Description: The server compiles and runs OK, DBM authorisation doesn't work. When an attempt to load a page from an authorised directory is made, the authorisation fails, and the following lines are appended to the error log for the server: [Thu Dec 5 12:29:45 1996] access to /data/www/conf/passwords_emag failed for vif7, reason: could not open dbm auth file [Thu Dec 5 12:29:45 1996] access to /data/www/htdocs/nz/education/emag/members/index.htm failed for vif7, reason: DBM user ashby not found Apache 1.1.1 worked OK with exactly the same configuration. I have extracted the code that is responsible for openning the DBM file and wrapped a simple test harness around it to see if it will work independently of the server, and it does even when running under the same user/group as the server. >How-To-Repeat: # .htaccess file for EMAG members only area AuthDBMUserFile /data/www/conf/passwords_emag AuthDBMGroupFile /data/www/conf/passwords_emag AuthName members AuthType Basic require valid-user File access for password file: -rw-rw-r-- 1 bboard uucp 4096 Nov 7 13:50 /data/www/conf/passwords_emag.dir -rw-rw-r-- 1 bboard uucp 2048 Dec 5 11:41 /data/www/conf/passwords_emag.pag Server is running as user 'bboard', group 'uucp' >Fix: Not off hand, have had to go back to using 1.1. >Audit-Trail: State-Changed-From-To: open-feedback State-Changed-By: marc State-Changed-When: Fri Jan 24 21:34:58 PST 1997 State-Changed-Why: Can you confirm if this problem still exists in 1.2b4 or 1.2b5 (when it is released in the next few days)? State-Changed-From-To: feedback-closed State-Changed-By: marc State-Changed-When: Sat Feb 15 20:50:21 PST 1997 State-Changed-Why: No feedback, assuming closed. >Unformatted: