setauthent(3x) [ultrix 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 may be served by BIND/Hesiod, a separate Kerberos initialization is necessary prior to using any of the functions.

       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)
       %%DNSecUsers%%
       %%DNSecAdmin%%
       %%DNBIND/Hes%%

																    getauthuid(3x)

SYSTEM-AUTH-AC(5)						File Formats Manual						 SYSTEM-AUTH-AC(5)

NAME

       system-auth-ac,	password-auth-ac,  smartcard-auth-ac, fingerprint-auth-ac, postlogin-ac - Common configuration files for PAMified services
       written by authconfig(8)

SYNOPSIS

       /etc/pam.d/system-auth-ac

DESCRIPTION

       The purpose of this configuration file is to provide common configuration file  for  all  applications  and  service  daemons  calling  PAM
       library.

       The system-auth configuration file is included from all individual service configuration files with the help of the include directive. When
       authconfig(8) writes the system PAM configuration file it replaces the default system-auth file with a symlink pointing	to  system-auth-ac
       and writes the configuration to this file. The symlink is not changed on subsequent configuration changes even if it points elsewhere. This
       allows system administrators to override the configuration written by authconfig.

       The  authconfig	now  writes  the  authentication  modules  also  into  additional  PAM	configuration  files  /etc/pam.d/password-auth-ac,
       /etc/pam.d/smartcard-auth-ac, and /etc/pam.d/fingerprint-auth-ac.  These configuration files contain only modules which perform authentica-
       tion with the respective kinds of authentication tokens.  For example /etc/pam.d/smartcard-auth[-ac] will not contain pam_unix and pam_ldap
       modules and /etc/pam.d/password-auth[-ac] will not contain pam_pkcs11 and pam_fprintd modules.

       The  file  /etc/pam.d/postlogin-ac  contains  common services to be invoked after login. An example can be a module that encrypts an user's
       filesystem or user's keyring and is decrypted by his password.

       The PAM configuration files of services which are accessed by remote connections such as sshd or ftpd now include the  /etc/pam.d/password-
       auth configuration file instead of /etc/pam.d/system-auth.

EXAMPLE

       Configure  system  to  use  pam_tally2  for  configuration  of maximum number of failed logins. Also call pam_access to verify if access is
       allowed.

       Make system-auth symlink point to system-auth-local which contains:

       auth	       requisite       pam_access.so
       auth	       requisite       pam_tally2.so deny=3 lock_time=30 
					     unlock_time=3600
       auth	       include	       system-auth-ac
       account	       required        pam_tally2.so
       account	       include	       system-auth-ac
       password        include	       system-auth-ac
       session	       include	       system-auth-ac

BUGS

       None known.

SEE ALSO

       authconfig(8), authconfig-gtk(8), pam(8), system-auth(5)

Red Hat, Inc.							   2010 March 31						 SYSTEM-AUTH-AC(5)