RPC(3) BSD Programmer's Manual RPC(3)
auth_destroy, authnone_create, authunix_create, authunix_create_default - library routines for remote procedure calls
#include <rpc/rpc.h> void auth_destroy(AUTH *auth); AUTH * authnone_create(void); AUTH * authunix_create(char *host, int uid, int gid, int len, int *aup.gids); AUTH * authunix_create_default(void);
These routines establish authentication information for use by the RPC functions described in rpc(3). auth_destroy() is a 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(). authnone_create() creates and returns an RPC authentication handle that passes nonusable authentication information with each remote procedure call. This is the default authentication used by RPC. authunix_create() creates and returns an RPC authentication handle that contains UNIX 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. It is easy to imper- sonate a user. authunix_create_default() calls authunix_create() with the appropriate parameters.
rpcgen(1), select(2), getrpcport(3), rpc(3), xdr(3), rpc(5), portmap(8) Remote Procedure Calls: Protocol Specification. Remote Procedure Call Programming Guide. rpcgen Programming Guide. Sun Microsystems, Inc., RPC: Remote Procedure Call Protocol Specification, RFC 1057, USC-ISI. MirOS BSD #10-current February 16, 1988 1
Generated on 2014-07-04 21:17:45 by $MirOS: src/scripts/roff2htm,v 1.79 2014/02/10 00:36:11 tg Exp $
These manual pages and other documentation are copyrighted by their respective writers;
their source is available at our CVSweb,
AnonCVS, and other mirrors. The rest is Copyright © 2002‒2014 The MirOS Project, Germany.
This product includes material provided by Thorsten Glaser.
This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report – diffs preferred.