Lines Matching +full:application +full:- +full:dependent
8 rpcsec_gss \- security flavor incorporating GSS-API protections
12 cc [ \fIflag\fR... ] \fIfile\fR... -lnsl [ \fIlibrary\fR... ]
19 \fBRPCSEC_GSS\fR is a security flavor which sits "on top" of the \fBGSS-API\fR
21 \fBRPCSEC_GSS\fR can take advantage of \fBGSS-API\fR security features;
23 Kerberos) that works with the \fBGSS-API.\fR
26 The \fBGSS-API\fR offers two security services beyond the traditional
32 they wish to use. Type of security service is mechanism-independent.
35 Before exchanging data with a peer, an application must establish a context for
37 \fBrpc_gss_seccreate()\fR, which allows the application to specify the security
40 integrity or privacy, and is mechanism-dependent.) Once a context is
76 Structure containing options passed directly through to the \fBGSS-API.\fR
94 This data type is used by in-kernel RPC routines, and thus is mentioned here
109 Structure containing \fBGSS-API\fR options returned to the calling function,
129 The (mechanism-dependent, opaque) client principal type. Used as an argument
189 bool_t (*callback)(); /*user-defined callback routine*/
232 on which they are described. An (S) indicates it is a server-side function:
431 MT-Level MT-Safe