version 1, including all changes.
.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
dbmmanage |
|
|
2 |
!!!dbmmanage |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
OPTIONS |
|
|
7 |
BUGS |
|
|
8 |
SEE ALSO |
|
|
9 |
---- |
|
|
10 |
!!NAME |
|
|
11 |
|
|
|
12 |
|
|
|
13 |
dbmmanage - Create and update user authentication files in DBM format |
|
|
14 |
!!SYNOPSIS |
|
|
15 |
|
|
|
16 |
|
|
|
17 |
__dbmmanage__ ''filename'' [[ ''command'' ] [[ |
|
|
18 |
''username'' [[ ''encpasswd'' ] ] |
|
|
19 |
!!DESCRIPTION |
|
|
20 |
|
|
|
21 |
|
|
|
22 |
__dbmmanage__ is used to create and update the DBM format |
|
|
23 |
files used to store usernames and password for basic |
|
|
24 |
authentication of HTTP users. Resources available from the |
|
|
25 |
__apache__ Apache web server can be restricted to just |
|
|
26 |
the users listed in the files created by __dbmmanage.__ |
|
|
27 |
This program can only be used when the usernames are stored |
|
|
28 |
in a DBM file. To use a flat-file database see |
|
|
29 |
__htpasswd__. |
|
|
30 |
|
|
|
31 |
|
|
|
32 |
This manual page only lists the command line arguments. For |
|
|
33 |
details of the directives necessary to configure user |
|
|
34 |
authentication in __apache__ see the Apache manual, which |
|
|
35 |
is part of the Apache distribution or can be found at |
|
|
36 |
http://httpd.apache.org/. |
|
|
37 |
!!OPTIONS |
|
|
38 |
|
|
|
39 |
|
|
|
40 |
''filename'' |
|
|
41 |
|
|
|
42 |
|
|
|
43 |
The filename of the DBM format file. Usually without the |
|
|
44 |
extension .db, .pag, or .dir. |
|
|
45 |
|
|
|
46 |
|
|
|
47 |
''command'' |
|
|
48 |
|
|
|
49 |
|
|
|
50 |
This selects the operation to perform: |
|
|
51 |
|
|
|
52 |
|
|
|
53 |
__add__ Adds an entry for ''username'' to |
|
|
54 |
''filename'' using the encrypted password |
|
|
55 |
''encpassword''. |
|
|
56 |
|
|
|
57 |
|
|
|
58 |
__adduser__ |
|
|
59 |
|
|
|
60 |
|
|
|
61 |
Asks for a password and then adds an entry for |
|
|
62 |
''username'' to ''filename'' . |
|
|
63 |
|
|
|
64 |
|
|
|
65 |
__check__ |
|
|
66 |
|
|
|
67 |
|
|
|
68 |
Asks for a password and then checks if ''username'' is in |
|
|
69 |
''filename'' and if it's password matches the specified |
|
|
70 |
one. |
|
|
71 |
|
|
|
72 |
|
|
|
73 |
__delete__ |
|
|
74 |
|
|
|
75 |
|
|
|
76 |
Deletes the ''username'' entry from |
|
|
77 |
''filename''. |
|
|
78 |
|
|
|
79 |
|
|
|
80 |
__import__ |
|
|
81 |
|
|
|
82 |
|
|
|
83 |
Reads username:password entries (one per line) from STDIN |
|
|
84 |
and adds them to ''filename''. The passwords already has |
|
|
85 |
to be crypted. |
|
|
86 |
|
|
|
87 |
|
|
|
88 |
__update__ |
|
|
89 |
|
|
|
90 |
|
|
|
91 |
Same as the |
|
|
92 |
username'' already exists in |
|
|
93 |
''filename''. |
|
|
94 |
|
|
|
95 |
|
|
|
96 |
__view__ Just displays the complete contents of the DBM |
|
|
97 |
file. |
|
|
98 |
|
|
|
99 |
|
|
|
100 |
''username'' |
|
|
101 |
|
|
|
102 |
|
|
|
103 |
The user for which the update operation is |
|
|
104 |
performed. |
|
|
105 |
!!BUGS |
|
|
106 |
|
|
|
107 |
|
|
|
108 |
One should be aware that there are a number of different DBM |
|
|
109 |
file formats in existance, and with all likelihood, |
|
|
110 |
libraries for more than one format may exist on your system. |
|
|
111 |
The three primary examples are NDBM, the GNU project's GDBM, |
|
|
112 |
and Berkeley DB 2. Unfortunately, all these libraries use |
|
|
113 |
different file formats, and you must make sure that the file |
|
|
114 |
format used by ''filename'' is the same format that |
|
|
115 |
__dbmmanage__ expects to see. __dbmmanage__ currently |
|
|
116 |
has no way of determining what type of DBM file it is |
|
|
117 |
looking at. If used against the wrong format, will simply |
|
|
118 |
return nothing, or may create a different DBM file with a |
|
|
119 |
different name, or at worst, it may corrupt the DBM file if |
|
|
120 |
you were attempting to write to it. |
|
|
121 |
|
|
|
122 |
|
|
|
123 |
__dbmmanage__ has a list of DBM format preferences, |
|
|
124 |
defined by the __@AnyDBM::ISA__ array near the beginning |
|
|
125 |
of the program. Since we prefer the Berkeley DB 2 file |
|
|
126 |
format, the order in which __dbmmanage__ will look for |
|
|
127 |
system libraries is Berkeley DB 2, then NDBM, and then GDBM. |
|
|
128 |
The first library found will be the library __dbmmanage__ |
|
|
129 |
will attempt to use for all DBM file transactions. This |
|
|
130 |
ordering is slightly different than the standard |
|
|
131 |
__@AnyDBM::ISA__ ordering in perl, as well as the |
|
|
132 |
ordering used by the simple dbmopen() call in Perl, so if |
|
|
133 |
you use any other utilities to manage your DBM files, they |
|
|
134 |
must also follow this preference ordering. Similar care must |
|
|
135 |
be taken if using programs in other languages, like C, to |
|
|
136 |
access these files. |
|
|
137 |
|
|
|
138 |
|
|
|
139 |
Apache's __mod_auth_db.c__ module corresponds to Berkeley |
|
|
140 |
DB 2 library, while __mod_auth_dbm.c__ corresponds to the |
|
|
141 |
NDBM library. Also, one can usually use the __file__ |
|
|
142 |
program supplied with most Unix systems to see what format a |
|
|
143 |
DBM file is in. |
|
|
144 |
!!SEE ALSO |
|
|
145 |
|
|
|
146 |
|
|
|
147 |
__apache(8)__ |
|
|
148 |
---- |