|
|
|
getprpwnam(3) -- manipulate protected password database entries (for trusted systems only).
|
|
getprpwent, getprpwuid, getprpwaid, and getprpwnam each returns a pointer to a pr_passwd structure containing the broken-out fields of a line in the protected password database. Each line in the database contains a pr_passwd structure, declared in the header file: struct pr_field { /* Identity: */ char fd_name[9]; /* uses 8 character maximum(and NULL) from utmp */ uid_t fd_uid; /* uid ass... |
|
getprpwuid(3) -- manipulate protected password database entries (for trusted systems only).
|
|
getprpwent, getprpwuid, getprpwaid, and getprpwnam each returns a pointer to a pr_passwd structure containing the broken-out fields of a line in the protected password database. Each line in the database contains a pr_passwd structure, declared in the header file: struct pr_field { /* Identity: */ char fd_name[9]; /* uses 8 character maximum(and NULL) from utmp */ uid_t fd_uid; /* uid ass... |
|
|
getprtcent(3) -- manipulate terminal control database entry for a trusted system
|
|
getprtcent and getprtcnam each returns a pointer to an object with the following structure containing the broken-out fields of an entry in the terminal control database. Each entry in the database contains a pr_term structure, declared in the header file: struct t_field { char fd_devname[14]; /* Terminal (or host) name */ uid_t fd_uid; /* uid of last successful login */ time_t fd_slogin; ... |
|
getprtcnam(3) -- manipulate terminal control database entry for a trusted system
|
|
getprtcent and getprtcnam each returns a pointer to an object with the following structure containing the broken-out fields of an entry in the terminal control database. Each entry in the database contains a pr_term structure, declared in the header file: struct t_field { char fd_devname[14]; /* Terminal (or host) name */ uid_t fd_uid; /* uid of last successful login */ time_t fd_slogin; ... |
|
getresgid(3) -- get real, effective and saved user or group IDs
|
|
getresuid and getresgid return the real, effective, and saved user or group ID's of the current process. |
|
getresuid(3) -- get real, effective and saved user or group IDs
|
|
getresuid and getresgid return the real, effective, and saved user or group ID's of the current process. |
|
get_secdef_int(3) -- security defaults configuration file routines
|
|
open_secdef opens the security configuration file /etc/default/security. This function must be called prior to calling get_secdef_str or get_secdef_int. close_secdef closes the security configuration file. get_secdef_str and get_secdef_int return the value of the specified parameter defined in the security configuration file. See the security(4) manpage. Programs using these routines must be compi... |
|
get_secdef_str(3) -- security defaults configuration file routines
|
|
open_secdef opens the security configuration file /etc/default/security. This function must be called prior to calling get_secdef_str or get_secdef_int. close_secdef closes the security configuration file. get_secdef_str and get_secdef_int return the value of the specified parameter defined in the security configuration file. See the security(4) manpage. Programs using these routines must be compi... |
|
gfrt0.o(3) -- 64-bit ELF uses crt0.o only
|
|
PA-RISC 32-bit SOM The C, Pascal, and FORTRAN compilers link in the object files crt0.o, gcrt0.o, or mcrt0.o to provide startup capabilities and environments for program execution. All are identical except that gcrt0.o and mcrt0.o provide additional functionality for gpro profiling support respectively. The following symbols are defined in these object files: _environ An array of character pointer... |
|
gfrt0.o_pa(3) -- 64-bit ELF uses crt0.o only
|
|
PA-RISC 32-bit SOM The C, Pascal, and FORTRAN compilers link in the object files crt0.o, gcrt0.o, or mcrt0.o to provide startup capabilities and environments for program execution. All are identical except that gcrt0.o and mcrt0.o provide additional functionality for gpro profiling support respectively. The following symbols are defined in these object files: _environ An array of character pointer... |
|
gss_accept_sec_context(3) -- establish a security context between the application and a context acceptor
|
|
The gss_accept_sec_context() routine is the second step in establishing a security context between the context initiator and a context acceptor. In the first step, the context initiator calls the gss_init_sec_context() routine. The gss_init_sec_context() routine generates a token for the security context and passes it to the context initiator. The context initiator sends the token to the context a... |
|
gss_acquire_cred(3) -- allow an application to acquire a handle for an existing, named credential
|
|
The gss_acquire_cred() routine allows an application to obtain a handle for a pre-existing credential by name. The credentials could be either an ACCEPT, INITIATE, or BOTH. The application then passes the credential handle to either the gss_init_sec_context() or the gss_accept_sec_context() routine. If desired_name is GSS_C_NO_NAME, the call is interpreted as a request for a credential handle that... |
|
gss_add_cred(3) -- adds a credential-element to a credential
|
|
The gss_add_cred() routine adds a credential-element to a credential. The credential-element is identified by the name of the principal to which it refers. If desired_name is GSS_C_NO_NAME, the call is interpreted as a request to add a credential element that will invoke default behavior when passed to gss_init_sec_context() or gss_accept_sec_context(). This routine can be used to either compose a... |
|
gss_add_oid_set_member(3) -- add an Object Identifier (OID) to an OID set
|
|
The gss_add_oid_set_member() routine adds a new Object Identifier to an Object Identifier set. If an OID set does not exist, you can create a new, empty OID set with the gss_create_empty_oid_set() routine. |
|
gss_canonicalize_name(3) -- convert an internal name to an internal mechanism name (MN) representation of an opaque internal name
|
|
The gss_canonicalize_name() routine generate a canonical mechanism name (MN) from an arbitrary internal name. The mechanism name is the name that would be returned to a context acceptor on successful authentication of a context where the initiator used the input_name in a successful call to gss_acquire_cred(), specifying an Object Identifier (OID) set containing mech_type as its only member, follo... |
