Lines Matching +full:per +full:- +full:context

1 .\" -*- nroff -*-
33 .Nd Initiate a security context with a peer application
55 Initiates the establishment of a security context between the
66 of the output_token argument to zero. To complete the context
85 .Bd -literal
89 input_token->length = 0;
109   if (output_token->length != 0) {
131 .Dv GSS_S_CONTINUE_NEEDED, the context is not fully established and the
133 .Bl -bullet
141 .Dv GSS_C_PROT_READY_FLAG, indicating that per-message services may be
159 implementation expects would be valid if context establishment
170 may choose to abort the context establishment by calling
174 context establishment (if the service was merely desired but not
184 returns, whether or not the context is fully established.
186 GSS-API implementations that support per-message protection are
193 behavior as the flag was not defined in Version 1 of the GSS-API.
194 Instead, applications should determine what per-message services
195 are available after a successful context establishment according
209 implementation should not create a context object, and should leave
215 implementation is permitted to delete the "half-built" security
216 context (in which case it should set the
220 security context untouched for the application to delete (using
223 During context establishment, the informational status bits
226 GSS-API mechanisms should always return them in association with a
230 exist in version 1 of the GSS-API specification, so applications that
231 wish to run over version 1 implementations must special-case these
234 .Bl -tag -width ".It initiator_cred_handle"
245 context handle for new context.  Supply
248 Resources associated with this context-handle
260 which requests that the context support a
264 flags should be logically-ORed
265 together to form the bit-mask value.  The
267 .Bl -tag -width "WW"
269 .Bl -tag -width "False"
276 .Bl -tag -width "False"
283 .Bl -tag -width "False"
293 .Bl -tag -width "False"
295 Enable detection of out-of-sequence protected messages
297 Don't attempt to detect out-of-sequence messages
300 .Bl -tag -width "False"
305 No per-message confidentiality service is required.
308 .Bl -tag -width "False"
315 No per-message integrity service is required.
318 .Bl -tag -width "False"
326 Desired number of seconds for which context
330 Application-specified bindings.  Allows
333 context.  Specify
346 storage that should be treated as read-only;
360 indicates that the context supports a specific
366 logically-ANDed with the
370 context.  The flags are:
371 .Bl -tag -width "WW"
373 .Bl -tag -width "False"
380 .Bl -tag -width "False"
387 .Bl -tag -width "False"
394 .Bl -tag -width "False"
396 Out-of-sequence protected messages will be detected
398 Out-of-sequence messages will not be detected
401 .Bl -tag -width "False"
411 data-origin authentication and
415 .Bl -tag -width "False"
423 Per-message integrity service unavailable.
426 .Bl -tag -width "False"
436 .Bl -tag -width "False"
457 .Bl -tag -width "False"
459 The resultant security context may be transferred to other processes via
463 The security context is not transferable.
469 Number of seconds for which the context
471 not support context expiration, the value
476 .Bl -tag -width ".It GSS_S_CREDENTIALS_EXPIRED"
482 context, and that gss_init_sec_context
492 context initiation, or the credential handle
505 error during context establishment
509 fatal error during context establishment.
511 Indicates that the supplied context handle did
512 not refer to a valid context
517 The provided target_name parameter was ill-formed.
530 .Bl -tag -width ".It RFC 2743"
534 Generic Security Service API Version 2 : C-bindings