dbmmanage.html revision 5c16955d1899c4f64dee2523b71be8deb6c96c57
842ae4bd224140319ae7feec1872b93dfd491143fielding<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
842ae4bd224140319ae7feec1872b93dfd491143fielding "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
842ae4bd224140319ae7feec1872b93dfd491143fielding
842ae4bd224140319ae7feec1872b93dfd491143fielding<html xmlns="http://www.w3.org/1999/xhtml">
842ae4bd224140319ae7feec1872b93dfd491143fielding <head>
842ae4bd224140319ae7feec1872b93dfd491143fielding <meta name="generator" content="HTML Tidy, see www.w3.org" />
1f728f035fca81594193e198b40bfa732b1c02ebtrawick
ce9621257ef9e54c1bbe5ad8a5f445a1f211c2dcnd <title>Manual Page: dbmmanage - Apache HTTP Server</title>
1f728f035fca81594193e198b40bfa732b1c02ebtrawick </head>
ce9621257ef9e54c1bbe5ad8a5f445a1f211c2dcnd
ce9621257ef9e54c1bbe5ad8a5f445a1f211c2dcnd <body bgcolor="#ffffff" text="#000000" link="#0000ff"
ce9621257ef9e54c1bbe5ad8a5f445a1f211c2dcnd vlink="#000080" alink="#ff0000">
ce9621257ef9e54c1bbe5ad8a5f445a1f211c2dcnd <div align="center">
ce9621257ef9e54c1bbe5ad8a5f445a1f211c2dcnd <img src="/images/sub.gif" alt="[APACHE DOCUMENTATION]" />
1f728f035fca81594193e198b40bfa732b1c02ebtrawick
1f728f035fca81594193e198b40bfa732b1c02ebtrawick <h3>Apache HTTP Server Version 2.1</h3>
9d129b55f5a43abf43865c6b0eb6dd19bc22aba8ianh </div>
9d129b55f5a43abf43865c6b0eb6dd19bc22aba8ianh
9d129b55f5a43abf43865c6b0eb6dd19bc22aba8ianh
9d129b55f5a43abf43865c6b0eb6dd19bc22aba8ianh
9d129b55f5a43abf43865c6b0eb6dd19bc22aba8ianh <h1 align="center">Manual Page: dbmmanage</h1>
9d129b55f5a43abf43865c6b0eb6dd19bc22aba8ianh <!-- This document was autogenerated from the man page -->
9d129b55f5a43abf43865c6b0eb6dd19bc22aba8ianh<pre>
9d129b55f5a43abf43865c6b0eb6dd19bc22aba8ianh<strong>NAME</strong>
9d129b55f5a43abf43865c6b0eb6dd19bc22aba8ianh dbmmanage - Create and update user authentication files in
1f728f035fca81594193e198b40bfa732b1c02ebtrawick DBM format
1f728f035fca81594193e198b40bfa732b1c02ebtrawick
1f728f035fca81594193e198b40bfa732b1c02ebtrawick<strong>SYNOPSIS</strong>
1f728f035fca81594193e198b40bfa732b1c02ebtrawick <strong>dbmmanage</strong> <em>filename</em> [ <em>command</em> ] [ <em>username</em> [ <em>encpasswd</em> ] ]
1f728f035fca81594193e198b40bfa732b1c02ebtrawick
1f728f035fca81594193e198b40bfa732b1c02ebtrawick<strong>DESCRIPTION</strong>
1f728f035fca81594193e198b40bfa732b1c02ebtrawick <strong>dbmmanage</strong> is used to create and update the DBM format files
1f728f035fca81594193e198b40bfa732b1c02ebtrawick used to store usernames and password for basic authentica-
1f728f035fca81594193e198b40bfa732b1c02ebtrawick tion of HTTP users. Resources available from the <strong>httpd</strong>
2a503ad7fa6fc3572647e915a0d7f31a17d11b1drbb Apache web server can be restricted to just the users listed
3a50e4da8a0db4515ab45678e5b39ff7e7594320trawick in the files created by <strong>dbmmanage.</strong> This program can only be
1f728f035fca81594193e198b40bfa732b1c02ebtrawick used when the usernames are stored in a DBM file. To use a
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc flat-file database see <strong>htpasswd</strong>.
886cd69ebf69e990dbc365be87ff8ea7cd681904rbb
2a503ad7fa6fc3572647e915a0d7f31a17d11b1drbb This manual page only lists the command line arguments. For
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc details of the directives necessary to configure user
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc authentication in <strong>httpd</strong> see the Apache manual, which is part
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc of the Apache distribution or can be found at
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc http://www.apache.org/.
2a503ad7fa6fc3572647e915a0d7f31a17d11b1drbb
2a503ad7fa6fc3572647e915a0d7f31a17d11b1drbb<strong>OPTIONS</strong>
1f728f035fca81594193e198b40bfa732b1c02ebtrawick <em>filename</em>
67f6dca9f3c35eb904c7b29a220db6c4482374dctrawick The filename of the DBM format file. Usually without
67f6dca9f3c35eb904c7b29a220db6c4482374dctrawick the extension .db, .pag, or .dir.
67f6dca9f3c35eb904c7b29a220db6c4482374dctrawick
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc <em>command</em>
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc This selects the operation to perform:
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc <strong>add </strong> Adds an entry for <em>username</em> to <em>filename</em> using the
67f6dca9f3c35eb904c7b29a220db6c4482374dctrawick encrypted password <em>encpassword</em>.
67f6dca9f3c35eb904c7b29a220db6c4482374dctrawick
67f6dca9f3c35eb904c7b29a220db6c4482374dctrawick <strong>adduser </strong> Asks for a password and then adds an entry for
67f6dca9f3c35eb904c7b29a220db6c4482374dctrawick <em>username</em> to <em>filename</em> .
67f6dca9f3c35eb904c7b29a220db6c4482374dctrawick
67f6dca9f3c35eb904c7b29a220db6c4482374dctrawick <strong>check </strong> Asks for a password and then checks if <em>username</em>
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc is in <em>filename</em> and if it's password matches the
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc specified one.
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc <strong>delete </strong> Deletes the <em>username</em> entry from <em>filename</em>.
67f6dca9f3c35eb904c7b29a220db6c4482374dctrawick
67f6dca9f3c35eb904c7b29a220db6c4482374dctrawick <strong>import </strong> Reads username:password entries (one per line)
67f6dca9f3c35eb904c7b29a220db6c4482374dctrawick from STDIN and adds them to <em>filename</em>. The pass-
8d290205047d88e37555019fe9a26f1c5ece7023gregames words already has to be crypted.
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc
8d290205047d88e37555019fe9a26f1c5ece7023gregames <strong>update </strong> Same as the "adduser" command, except that it
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc makes sure <em>username</em> already exists in <em>filename</em>.
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc <strong>view </strong> Just displays the complete contents of the DBM
c6a06ed5b9ec5600bedefc11bbc22919fe170ad4jailletc file.
8d290205047d88e37555019fe9a26f1c5ece7023gregames
8d290205047d88e37555019fe9a26f1c5ece7023gregames <em>username</em> The user for which the update operation is per-
8d290205047d88e37555019fe9a26f1c5ece7023gregames formed.
db3fa7db7c7910f2f23c3e3ffe0cf9f41a1899b9trawick
67f6dca9f3c35eb904c7b29a220db6c4482374dctrawick<strong>BUGS</strong>
67f6dca9f3c35eb904c7b29a220db6c4482374dctrawick One should be aware that there are a number of different DBM
67f6dca9f3c35eb904c7b29a220db6c4482374dctrawick file formats in existence, and with all likelihood,
67f6dca9f3c35eb904c7b29a220db6c4482374dctrawick libraries for more than one format may exist on your system.
8d290205047d88e37555019fe9a26f1c5ece7023gregames The three primary examples are NDBM, the GNU project's GDBM,
8d290205047d88e37555019fe9a26f1c5ece7023gregames and Berkeley DB 2. Unfortunately, all these libraries use
db3fa7db7c7910f2f23c3e3ffe0cf9f41a1899b9trawick different file formats, and you must make sure that the file
12d7cc79eeb598697b4c9046991035d91fac2476nd format used by <em>filename</em> is the same format that <strong>dbmmanage</strong>
12d7cc79eeb598697b4c9046991035d91fac2476nd expects to see. <strong>dbmmanage</strong> currently has no way of determin-
12d7cc79eeb598697b4c9046991035d91fac2476nd ing what type of DBM file it is looking at. If used against
12d7cc79eeb598697b4c9046991035d91fac2476nd the wrong format, will simply return nothing, or may create
12d7cc79eeb598697b4c9046991035d91fac2476nd a different DBM file with a different name, or at worst, it
1f728f035fca81594193e198b40bfa732b1c02ebtrawick may corrupt the DBM file if you were attempting to write to
9d129b55f5a43abf43865c6b0eb6dd19bc22aba8ianh it.
<strong>dbmmanage</strong> has a list of DBM format preferences, defined by
the <strong>@AnyDBM::ISA</strong> array near the beginning of the program.
Since we prefer the Berkeley DB 2 file format, the order in
which <strong>dbmmanage</strong> will look for system libraries is Berkeley
DB 2, then NDBM, and then GDBM. The first library found
will be the library <strong>dbmmanage</strong> will attempt to use for all
DBM file transactions. This ordering is slightly different
than the standard <strong>@AnyDBM::ISA</strong> 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.
Apache's <strong>mod_auth_dbm.c</strong> corresponds to the NDBM
library. Also, one can usually use the <strong>file</strong> program sup-
plied with most Unix systems to see what format a DBM file
is in.
<strong>SEE ALSO</strong>
<strong>httpd(8)</strong>
</pre>
<hr />
<h3 align="center">Apache HTTP Server Version 2.1</h3>
<a href="./"><img src="/images/index.gif" alt="Index" /></a>
<a href="../"><img src="/images/home.gif" alt="Home" /></a>
</body>
</html>