A LINCKS database includes several files, which we will briefly describe in this section.
Users can change their passwords by using the dbpasswd program (independent of whether they are clear text or encrypted). The passwd file should be readable by the database owner only, and dbpasswd is installed suid so that the file can be updated.
The only way to change a username is to edit file.
The groups file contains the mapping of user id's to the protection groups of which they are members. The file's syntax is:
0 1 2 3 4*
2 1 2*
which means that user 0 has read-write access to objects created by users 1 through 4, and user 2 has read-write access to objects created by users 1 and 2. The asterix marks the end of the definition set for each uid's membership groups.
The wrgroups file contains the mapping of user IDs to the protection groups of which they are members and thus which objects they are allowed to change. The file's syntax is:
0 1 2 3 4*
2 1 2*
which means that user 0 has write access to objects created by users 1 through 4, and user 2 has write access to objects created by users 1 and 2. The asterix marks the end of the definition for each uid's membership groups.
Notice that wrgroups is only in effect if it is present and then defines the write access for the different users. If the file is not present, only the restriction imposed by the groups file is used both for read and write access to objects.
In the .lincksrc file, we refer to the directory with all these files as DBDIR.