Lines Matching +full:in +full:- +full:application

1 .\" -*- nroff -*-
6 .\" Redistribution and use in source and binary forms, with or without
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\"    notice, this list of conditions and the following disclaimer in the
18 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
22 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
23 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
33 .Nd Initiate a security context with a peer application
56 application and a remote peer.
61 the peer application, where the peer application will present it to
68 application; if so,
76 application, passing the reply token to
85 .Bd -literal
89 input_token->length = 0;
109   if (output_token->length != 0) {
133 .Bl -bullet
141 .Dv GSS_C_PROT_READY_FLAG, indicating that per-message services may be
142 applied in advance of a successful completion status, the value
160 were to succeed.  In particular, if the application has requested
169 argument that the service will not be supported.  The application
172 (if it cannot continue in the absence of
186 GSS-API implementations that support per-message protection are
188 .Dv GSS_C_PROT_READY_FLAG in the final
193 behavior as the flag was not defined in Version 1 of the GSS-API.
194 Instead, applications should determine what per-message services
214 indicate this.  In the event of a failure on a subsequent call, the
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
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"
247 returned by first call in continuation calls.
248 Resources associated with this context-handle
249 must be released by the application after use
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"
330 Application-specified bindings.  Allows
331 application to securely bind channel
337 Token received from peer application.
346 storage that should be treated as read-only;
347 In particular the application should not attempt
351 token to be sent to peer application.  If
354 application.  Storage associated with this
355 buffer must be freed by the application
366 logically-ANDed with the
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"
476 .Bl -tag -width ".It GSS_S_CREDENTIALS_EXPIRED"
481 application is required to complete the
517 The provided target_name parameter was ill-formed.
530 .Bl -tag -width ".It RFC 2743"
532 Generic Security Service Application Program Interface Version 2, Update 1
534 Generic Security Service API Version 2 : C-bindings
539 function first appeared in
548 or assist in its implementation may be prepared, copied, published
549 and distributed, in whole or in part, without restriction of any
552 document itself may not be modified in any way, such as by removing
555 developing Internet standards in which case the procedures for
556 copyrights defined in the Internet Standards process must be