dbmmanage is used to create and update the DBM format files used to store usernames and password for basic authentication of HTTP users via
mod_authn_dbm. Resources available from the Apache HTTP server can be restricted to just the users listed in the files created by
dbmmanage. This program can only be used when the usernames are stored in a DBM file. To use a flat-file database see
Another tool to maintain a DBM password database is
This manual page only lists the command line arguments. For details of the directives necessary to configure user authentication in
httpd see the httpd manual, which is part of the Apache distribution or can be found at http://httpd.apache.org/.
dbmmanage [ encoding ] filename add|adduser|check|delete|update username [ encpasswd [ group[,group...] [ comment ] ] ]
dbmmanage filename view [ username ]
dbmmanage filename import
addcommands. You may use a hyphen (
-) if you want to get prompted for the password, but fill in the fields afterwards. Additionally when using the
updatecommand, a period (
.) keeps the original password untouched.
:). You may use a hyphen (
-) if you don't want to assign the user to a group, but fill in the comment field. Additionally when using the
updatecommand, a period (
.) keeps the original groups untouched.
dbmmanage passwords.dat add rbowen foKntnEF3KSXA
dbmmanage passwords.dat adduser krietz
dbmmanage passwords.dat check rbowen
dbmmanage passwords.dat delete rbowen
username:passwordentries (one per line) from
STDINand adds them to filename. The passwords already have to be crypted.
addusercommand, except that it makes sure username already exists in filename.
dbmmanage passwords.dat update rbowen
dbmmanage passwords.dat view
One should be aware that there are a number of different DBM file formats in existence, and with all likelihood, libraries for more than one format may exist on your system. The three primary examples are SDBM, NDBM, the GNU project's GDBM, and Berkeley DB 2. Unfortunately, all these libraries use different file formats, and you must make sure that the file format used by filename is the same format that
dbmmanage expects to see.
dbmmanage currently has no way of determining what type of DBM file it is looking at. If used against the wrong format, will simply return nothing, or may create a different DBM file with a different name, or at worst, it may corrupt the DBM file if you were attempting to write to it.
dbmmanage has a list of DBM format preferences, defined by the
@AnyDBM::ISA array near the beginning of the program. Since we prefer the Berkeley DB 2 file format, the order in which
dbmmanage will look for system libraries is Berkeley DB 2, then NDBM, then GDBM and then SDBM. The first library found will be the library
dbmmanage will attempt to use for all DBM file transactions. This ordering is slightly different than the standard
@AnyDBM::ISA ordering in Perl, as well as the ordering used by the simple
dbmopen() call in Perl, so if you use any other utilities to manage your DBM files, they must also follow this preference ordering. Similar care must be taken if using programs in other languages, like C, to access these files.
One can usually use the
file program supplied with most Unix systems to see what format a DBM file is in.
© 2017 The Apache Software Foundation
Licensed under the Apache License, Version 2.0.