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

1 .\" -*- nroff -*-
33 .Nd Accept a security context initiated by a peer application
53 Allows a remotely initiated security context between the application and a remote
66 To complete the context establishment, one or more reply tokens may be
84 .Bd -literal
103   if (output_token->length != 0) {
119 .Dv GSS_S_CONTINUE_NEEDED , the context is not fully established and the
128 .Dv GSS_C_PROT_READY_FLAG , indicating that per-message services may be
148 implementation expects would be valid if context establishment were
159 returns, whether or not the context is fully established.
161 Although this requires that GSS-API implementations set the
169 should not rely on this behavior as the flag was not defined in Version 1 of the GSS-API.
170 Instead, applications should be prepared to use per-message services after a
171 successful context establishment, according to the
184 implementation expects to be available from the established context.
189 implementation should not create a context object, and should leave
194 permitted to delete the "half-built" security context (in which case it
199 security context (and the context_handle parameter) untouched for the
203 During context establishment, the informational status bits
208 GSS-API mechanisms should always return them in association with a
211 exist in version 1 of the GSS-API specification, so applications that
212 wish to run over version 1 implementations must special-case these
215 .Bl -tag -width ".It input_chan_bindings"
217 Context handle for new context.
225 assigned to the corresponding context, and must
230 Credential handle claimed by context acceptor.
232 .Dv GSS_C_NO_CREDENTIAL to accept the context as a
242 Application-specified bindings.
244 to the security context.
248 Authenticated name of context initiator.
256 and should be treated as read-only by the caller
264 If a non-zero length field is returned,
270 each of which indicates that the context supports a specific service option.
275 logically-ANDed with the
277 value to test whether a given option is supported by the context.
279 .Bl -tag -width "WW"
281 .Bl -tag -width "False"
288 .Bl -tag -width "False"
295 .Bl -tag -width "False"
302 .Bl -tag -width "False"
304 Out-of-sequence protected messages will be detected
306 Out-of-sequence messages will not be detected
309 .Bl -tag -width "False"
320 data-origin authentication and integrity services only.
323 .Bl -tag -width "False"
331 Per-message integrity service unavailable.
334 .Bl -tag -width "False"
343 .Bl -tag -width "False"
362 .Bl -tag -width "False"
364 The resultant security context may be transferred to other processes
368 The security context is not transferable.
374 Number of seconds for which the context will remain valid.
380 handle for credentials received from context initiator.
403 .Bl -tag -width ".It GSS_S_DEFECTIVE_CREDENTIAL"
406 complete the context,
413 The supplied credentials were not valid for context acceptance,
421 Indicates that the supplied context handle did not refer to a valid context.
426 This is a fatal error during context establishment.
430 This is a fatal error during context establishment.
445 .Bl -tag -width ".It RFC 2743"
449 Generic Security Service API Version 2 : C-bindings