gssapi.5 (2010 09)
g
gssapi(5) gssapi(5)
system. Therefore portable applications should use either the correct address type and value or the
GSS_C_AF_NULLADDR
for the initiator_addrtype
address field. Some security mechanisms
include the channel binding data in the token instead of a signature, so portable applications should not
use confidential data as channel-binding components. The GSSAPI does not verify the address or include
the plain text bindings information in the token.
Optional Parameters
In routine descriptions, optional parameters allow the application to request default behaviors by passing
a default value for the parameter. The following conventions are used for optional parameters:
Convention Value Default Explanation
For an input parameter,
indicates no data is sup-
plied. For an output
parameter, indicates that
the information returned is
not required by the applica-
tion.
gss_buffer_t types GSS_C_NO_BUFFER
Refer to the reference
pages for default values.
Integer types (input)
Indicates that the applica-
tion does not require the
information.
Integer types (output) NULL
Indicates that the applica-
tion does not require the
information.
Pointer types (output) NULL
Indicates the default choice
for name type or security
mechanism.
OIDs GSS_C_NULL_OID
Indicates the default set of
security mechanisms
OID sets GSS_C_NULL_OID_SET
Indicates that the applica-
tion should use the default
credential handle.
Credentials GSS_C_NO_CREDENTIAL
Indicates that no channel
bindings are used.
Channel bindings GSS_C_NO_CHANNEL_BINDINGS
SEE ALSO
gss_accept_sec_context(3), gss_compare_name(3), gss_display_name(3), gss_import_name(3),
gss_init_sec_context(3), gss_release_buffer(3), gss_release_oid_set(3), libgss(4).
RFC 2743, RFC 2744.
The manpages for DCE-GSSAPI are included with the DCE-CoreTools product. To see those manpages
add
/opt/dce/share/man to MANPATH.
HP-UX 11i Version 3: September 2010 − 7 − Hewlett-Packard Company 7