MAN page from PCLinuxOS lib64tirpc-devel-1.0.1-1pclos2017.x86_64.rpm
Section: C Library Functions (3)Index
- create a security context using the RPCSEC_GSS protocol
In rpc/rpcsec_gss.hFt AUTH *Fo rpc_gss_seccreateFa CLIENT *clntFa const char *principalFa const char *mechanismFa rpc_gss_service_t serviceFa const char *qopFa rpc_gss_options_req_t *options_reqFa rpc_gss_options_ret_t *options_retFc
This function is used to establish a security context between anapplication and a remote peer using the RPSEC_GSS protocol.
- An RPC handle which is connected to the remote peer
- The name of the service principal on the remote peer.For instance, a principal such asQq nfsAATTserver.example.commight be used by an application which needs to contact an NFS server
- The name of the GSS_API mechanism to use for the new security context."kerberos_v5" is currently the only supported mechanism.
- Type of service requested.
- The default - typically the same asrpc_gss_svc_none
- RPC headers only are integrity protected by a checksum.
- RPC headers and data are integrity protected by a checksum.
- RPC headers are integrity protected by a checksum and data is encrypted.
- The name of the Quality of Protection to use for the new security context,or NULL to use the default QOP."GSS_C_QOP_DEFAULT" is currently the only supported QOP.
- Extra security context options to be passed to the underlying GSS-APImechanism.PassNULLto supply default values.
- Various values returned by the underlying GSS-API mechanism.PassNULLif these values are not required.
If the security context was created successfully, a pointer to anVt AUTHstructure that represents the context is returned.To use this security context for subsequent RPC calls, setclnt->cl_auth
to this value.
TheFn rpc_gss_seccreatefunction is part of libtirpc.
Thismanual page was written byAn Doug Rabson Aq dfrAATTFreeBSD.org .
- RETURN VALUES
- SEE ALSO
This document was created byman2html,using the manual pages.