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 Accept a security context initiated by a peer application
53 Allows a remotely initiated security context between the application and a remote
57 which should be transferred to the peer application,
58 where the peer application will present it to
67 required from the peer application; if so,
70 .Dv GSS_S_CONTINUE_NEEDED , in which case it
72 application, passing the token to
84 .Bd -literal
103   if (output_token->length != 0) {
128 .Dv GSS_C_PROT_READY_FLAG , indicating that per-message services may be
129 applied in advance of a successful completion status, the value
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
194 permitted to delete the "half-built" security context (in which case it
200 application to delete (using
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"
220 call; use value returned in subsequent calls.
226 be freed by the application after use with a
240 Token obtained from remote application.
242 Application-specified bindings.
243 Allows application to securely bind channel identification information
256 and should be treated as read-only by the caller
261 Token to be passed to peer application.
263 then no token need be passed to the peer application.
264 If a non-zero length field is returned,
266 application with a call to
275 logically-ANDed with the
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"
394 the associated resources must be released by the application after use
403 .Bl -tag -width ".It GSS_S_DEFECTIVE_CREDENTIAL"
405 Indicates that a token from the peer application is required to
445 .Bl -tag -width ".It RFC 2743"
447 Generic Security Service Application Program Interface Version 2, Update 1
449 Generic Security Service API Version 2 : C-bindings
454 function first appeared in
463 or assist in its implementation may be prepared, copied, published
464 and distributed, in whole or in part, without restriction of any
467 document itself may not be modified in any way, such as by removing
470 developing Internet standards in which case the procedures for
471 copyrights defined in the Internet Standards process must be