rpc_gss_getcred man page on HP-UX

Man page or keyword search:  
man Server   10987 pages
apropos Keyword Search (all sections)
Output format
HP-UX logo
[printable version]

rpc_gss_getcred(3N)					   rpc_gss_getcred(3N)

NAME
       rpc_gss_getcred() - get credentials of client

SYNOPSIS

DESCRIPTION
       is  used	 by a server to fetch the credentials of a client.  These cre‐
       dentials may either be network credentials (in the form of a structure)
       or UNIX credentials.

       For more information on data types, see the rpcsec_gss(3N) manpage.

PARAMETERS
       Essentially,  passes  a pointer to a request as well as pointers to two
       credential structures and a user-defined cookie.	 If is	successful, at
       least  one  credential  structure  is  "filled out" with values, as is,
       optionally, the cookie.

       req	 Pointer to the received service request.  is an RPC structure
		 containing  information  on the context of an RPC invocation,
		 such as program, version, and transport information.

       rcred	 A pointer to an structure pointer.  This  structure  contains
		 the  version  number of the protocol being used; the security
		 mechanism and QOPs for this session (as  strings);  principal
		 names	for  the  client  (as  a  structure)  and server (as a
		 string); and the security service (integrity, privacy,	 etc.,
		 as an If an application is not interested in these values, it
		 may pass NULL for this parameter.

       ucred	 The caller's UNIX credentials, in the form of a pointer to  a
		 pointer  to  a structure, which includes the client's uid and
		 gids.	If an application is not interested in	these  values,
		 it may pass NULL for this parameter.

       cookie	 A  four-byte quantity that an application may use in any man‐
		 ner it wants to, because RPC does  not	 interpret  it.	  (For
		 example,  a  cookie  may be a pointer or index to a structure
		 that	represents   a	 context    initiator.)	    See	   the
		 rpc_gss_set_callback(3N) manpage.

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 and before These functions  should  not
       be  called  by  a  multithreaded application that supports asynchronous
       cancellation or asynchronous signals.

RETURN VALUE
       returns if it is successful; otherwise, use to get the error associated
       with the failure.

SEE ALSO
       rpc(3N),	  rpc_gss_set_callback(3N),   rpc_gss_set_svc_name(3N),	  rpc‐
       sec_gss(3N).

							   rpc_gss_getcred(3N)
[top]

List of man pages available for HP-UX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net