rpc_clnt_auth(3N)

NAME

rpc_clnt_auth: auth_destroy(), authnone_create(), authsys_create(), authsys_create_default() — library routines for client side remote procedure call authentication

SYNOPSIS

#include <rpc/rpc.h>

void auth_destroy(AUTH *auth);

AUTH *authnone_create(void);

AUTH *authsys_create(
const char *host,
const uid_t uid,
const gid_t gid,
const int len,
const gid_t *aup_gids);

AUTH *authsys_create_default(void);

DESCRIPTION

These routines are part of the RPC library that allows C language programs to make procedure calls on other machines across the network, with desired authentication.

These routines are normally called after creating the CLIENT handle. The cl_auth field of the CLIENT structure should be initialized by the AUTH structure returned by some of the following routines. The client's authentication information is passed to the server when the RPC call is made.

Only the NULL and the SYS style of authentication is discussed here. For the DES style authentication, please refer to secure_rpc(3N).

The NULL and SYS style of authentication are safe in multithreaded applications.

The HP-UX implementation of RPC only supports the X/Open Transport Interface (XTI). Applications that are written using the Transport Layer Interface (TLI) and wish to use RPC, must convert their application to XTI.

Routines

The following routines require that the header <rpc/rpc.h> be included (see rpc(3N) for the definition of the AUTH data structure).

void auth_destroy(): A function macro that destroys the authentication information associated with auth. Destruction usually involves deallocation of private data structures. The use of auth is undefined after calling auth_destroy().
AUTH *authnone_create(): Create and return an RPC authentication handle that passes nonusable authentication information with each remote procedure call. This is the default authentication used by RPC.
AUTH *authsys_create(): Create and return an RPC authentication handle that contains AUTH_SYS authentication information. The parameter host is the name of the machine on which the information was created; uid is the user's user ID; gid is the user's current group ID; len and aup_gids refer to a counted array of groups to which the user belongs.
AUTH *authsys_create_default(): Call authsys_create() with the appropriate parameters.

MULTITHREAD USAGE

Thread Safe:: Yes
Cancel Safe:: Yes
Fork Safe:: No
Async-cancel Safe:: No
Async-signal Safe:: No

These functions can be called safely in a multithreaded environment. They may be cancellation points in that they call functions that are cancel points.

In a multithreaded environment, these functions are not safe to be called by a child process after fork() and before exec(). These functions should not be called by a multithreaded application that supports asynchronous cancellation or asynchronous signals.

rpc_clnt_auth(3N)

Technical documentation

» Table of Contents

» Index

NAME

SYNOPSIS

DESCRIPTION

Routines

MULTITHREAD USAGE

SEE ALSO