| Main index | Section 3 | Options |
#include <rpc/rpcsec_gss.h>
| clnt | An RPC handle which is connected to the remote peer |
| principal | The name of the service principal on the remote peer. For instance, a principal such as "nfs@server.example.com" might be used by an application which needs to contact an NFS server |
| mechanism | The desired mechanism for this security context. The value of mechanism should be the name of one of the security mechanisms listed in /etc/gss/mech. |
| service | Type of service requested. |
| rpc_gss_svc_default | The default - typically the same as rpc_gss_svc_none. |
| rpc_gss_svc_none | RPC headers only are integrity protected by a checksum. |
| rpc_gss_svc_integrity | |
| RPC headers and data are integrity protected by a checksum. | |
| rpc_gss_svc_privacy | RPC headers are integrity protected by a checksum and data is encrypted. |
| qop | Desired quality of protection or NULL for the default. Available values are listed in /etc/gss/qop |
| options_req | Extra security context options to be passed to the underlying GSS-API mechanism. Pass NULL to supply default values. |
| options_ret | Various values returned by the underlying GSS-API mechanism. Pass NULL if these values are not required. |
| RPC_GSS_SECCREATE (3) | January 26, 2010 |
| Main index | Section 3 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
