Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

auth(5) [ultrix man page]

auth(5) 							File Formats Manual							   auth(5)

Name
       auth - auth database

Description
       The  database is a repository of security-relevant information about each user of the system. This database contains the encrypted password
       associated with the user's account in addition to a list of assorted capabilities.  The database is stored as an database in the files  and
       Records are retrieved with the library routine.	Access to the database is restricted to the superuser and members of the group

       Auth records may be converted to an ASCII representation whose format is:
       1000:4KvidFYwovnwp3j8lll78dC1:1920129:3600:2678400:03:0:1000:0:00:00
       The first field is the UID of the entry that is used as the key into the database. Then follows:

       Encrypted Password
		      This  is the user's encrypted password. Whether this password or the one from the file is actually used is determined by the
		      security level that the system is running at.

       Password Modification Time
		      This is the time(2) the password was last set.

       Minimum Password Lifetime
		      This is the minimum number of seconds which must elapse between setting passwords.

       Maximum Password Lifetime
		      This is the maximum period of time for which the password will be valid.

       Account Mask   These are capabilities pertaining to the account itself.	They are:

			 1 A_ENABLE: this account is enabled.
			 2 A_CHANGE_PASSWORD: The user can change his or her password.
			 4 A_ENTER_PASSWORD: The user is not required to use machine-generated passwords.

       Login Failure Count
		      This is the count of unsuccessful login attempts since the last successful login.

       Audit ID       Positive integer identifier used in generating audit records for the user.

       Audit Control  See the reference page, SET_APROC_CNTL section for more information.

       Audit Mask     Determines which events will be audited for the user. See the and reference pages for more information.

Restrictions
       Only the superuser and members of the group may read information from the auth database.  Only the superuser may modify the auth database.

Files
See Also
       audcntl(2), getauthuid(3), getpwent(3), edauth(8)

																	   auth(5)

Check Out this Related Man Page

getauthuid(3x)															    getauthuid(3x)

Name
       getauthuid, getauthent, storeauthent, setauthent, setauthfile, endauthent - get/set auth entry

Syntax
       #include <sys/types.h>
       #include <auth.h>

       AUTHORIZATION *getauthuid(uid)
       uid_t uid;

       AUTHORIZATION *getauthent()

       int storeauthent(auth)
       AUTHORIZATION *auth;

       void setauthent()

       void setauthfile(pathname)
       char *pathname;

       int endauthent()

Description
       The function looks up the auth entry for the specified user ID and returns a pointer to a static area containing it.

       The function retrieves the next sequential entry from the auth database and returns a pointer to a static area containing it.

       The function stores the specified auth entry into the local auth database, overwriting any existing entry with the same a_uid field.

       The  function  sets  a  pointer to the beginning of the auth database.  This function is used with to make multiple passes through the auth
       database.

       The function sets the pathname of the file to be used for the local auth database in all subsequent operations.

       The function closes the auth database.  Subsequent calls to getauthuid, getauthent, or storeauthent reopen it.

       The auth database can be distributed via the BIND/Hesiod naming service.

Restrictions
       Only the superuser and members of the group authread may read information from the auth database.

       Only the superuser may modify the auth database.

       The auth database cannot be distributed via the Yellow Pages service.

       When the auth database is served by BIND/Hesiod, a program must perform its own Kerberos initialization prior to using any of  these  func-
       tions.

       The values returned by and point to a static area which is overwritten when subsequent calls are made.

Return Values
       Functions which return a pointer value return the null pointer(0) on EOF or error.  Other functions return zero(0) on success and a nega-
       tive value on failure.

Files
See Also
       getpwent(3), auth(5), edauth(8)
       Security Guide for Users
       Security Guide for Administrators
       Guide to the BIND/Hesiod Service

																    getauthuid(3x)

Featured Tech Videos