dbmmanage - Manage authentication files in DBM format 2j5qj

Synopsis 5j6t5r

dbmmanage [ encoding ] filename add|add|check|delete|update name [ encwd [ group[,group...] [ comment ] ] ]

dbmmanage filename view [ name ]

dbmmanage filename import

Options 4y664e

filename

The filename of the DBM format file. Usually without the extension .db, .pag, or .dir.

name

The for which the operations are performed. The name may not contain a colon (:).

encwd

This is the already encrypted to use for the update and add commands. You may use a hyphen (-) if you want to get prompted for the , but fill in the fields afterwards. Additionally when using the update command, a period (.) keeps the original untouched.

group

A group, which the is member of. A groupname may not contain a colon (:). You may use a hyphen (-) if you don't want to assign the to a group, but fill in the comment field. Additionally when using the update command, a period (.) keeps the original groups untouched.

comment

This is the place for your opaque comments about the , like realname, mailaddress or such things. The server will ignore this field.

Encodings 44s1o

-d

crypt encryption (default, except on Win32, Netware)

-m

MD5 encryption (default on Win32, Netware)

-s

SHA1 encryption

-p

plaintext (not recommended)

Commands 1h622l

add

Adds an entry for name to filename using the encrypted encwd.

dbmmanage s.dat add rbowen foKntnEF3KSXA

add

Asks for a and then adds an entry for name to filename.

dbmmanage s.dat add krietz

check

Asks for a and then checks if name is in filename and if it's matches the specified one.

dbmmanage s.dat check rbowen

delete

Deletes the name entry from filename.

dbmmanage s.dat delete rbowen

import

Reads name: entries (one per line) from STDIN and adds them to filename. The s already have to be crypted.

update

Same as the add command, except that it makes sure name already exists in filename.

dbmmanage s.dat update rbowen

view

Just displays the contents of the DBM file. If you specify a name, it displays the particular record only.

dbmmanage s.dat view

Bugs a157

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.