1gss_wrap_size_limGietn(e3rGiScS)Security Services API LibrarygFsusn_cwtriaopn_ssize_limit(3GSS)
2
3
4
6 gss_wrap_size_limit - allow application to determine maximum message
7 size with resulting output token of a specified maximum size
8
10 cc [ flag... ] file... -lgss [ library... ]
11 #include <gssapi/gssapi.h>
12
13 OM_uint32 gss_process_context_token(OM_uint32 *minor_status,
14 const gss_ctx_id_t context_handle, int conf_req_flag,
15 gss_qop_t qop_req, OM_uint32 req_output_size,
16 OM_uint32 *max_input_size);
17
18
20 The gss_wrap_size_limit() function allows an application to determine
21 the maximum message size that, if presented to gss_wrap() with the same
22 conf_req_flag and qop_req parameters, results in an output token con‐
23 taining no more than req_output_size bytes. This call is intended for
24 use by applications that communicate over protocols that impose a maxi‐
25 mum message size. It enables the application to fragment messages prior
26 to applying protection. The GSS-API detects invalid QOP values when
27 gss_wrap_size_limit() is called. This routine guarantees only a maximum
28 message size, not the availability of specific QOP values for message
29 protection.
30
31
32 Successful completion of gss_wrap_size_limit() does not guarantee that
33 gss_wrap() will be able to protect a message of length max_input_size
34 bytes, since this ability might depend on the availability of system
35 resources at the time that gss_wrap() is called.
36
38 The parameter descriptions for gss_wrap_size_limit() are as follows:
39
40 minor_status A mechanism-specific status code.
41
42
43 context_handle A handle that refers to the security over which the
44 messages will be sent.
45
46
47 conf_req_flag Indicates whether gss_wrap() will be asked to apply
48 confidential protection in addition to integrity
49 protection. See gss_wrap(3GSS) for more details.
50
51
52 qop_req Indicates the level of protection that gss_wrap()
53 will be asked to provide. See gss_wrap(3GSS) for
54 more details.
55
56
57 req_output_size The desired maximum size for tokens emitted by
58 gss_wrap().
59
60
61 max_input_size The maximum input message size that can be presented
62 to gss_wrap() to guarantee that the emitted token
63 will be no larger than req_output_size bytes.
64
65
67 gss_wrap_size_limit() returns one of the following status codes:
68
69 GSS_S_COMPLETE Successful completion.
70
71
72 GSS_S_NO_CONTEXT The referenced context could not be accessed.
73
74
75 GSS_S_CONTEXT_EXPIRED The context has expired.
76
77
78 GSS_S_BAD_QOP The specified QOP is not supported by the
79 mechanism.
80
81
82 GSS_S_FAILURE The underlying mechanism detected an error for
83 which no specific GSS status code is defined.
84 The mechanism-specific status code reported by
85 means of the minor_status parameter details
86 the error condition.
87
88
90 See attributes(5) for descriptions of the following attributes:
91
92
93
94
95 ┌─────────────────────────────┬─────────────────────────────┐
96 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
97 ├─────────────────────────────┼─────────────────────────────┤
98 │Availability │SUNWgss (32-bit) │
99 ├─────────────────────────────┼─────────────────────────────┤
100 │ │SUNWgssx (64-bit) │
101 ├─────────────────────────────┼─────────────────────────────┤
102 │MT Level │Safe │
103 └─────────────────────────────┴─────────────────────────────┘
104
106 gss_wrap(3GSS), attributes(5)
107
108
109 Solaris Security for Developers Guide
110
111
112
113SunOS 5.11 15 Jan 2003 gss_wrap_size_limit(3GSS)