GSS_UNWRAP(3GSS) | Generic Security Services API Library Functions | GSS_UNWRAP(3GSS) |
gss_unwrap - verify a message with attached cryptographic message
cc [ flag... ] file... -lgss [ library... ] #include <gssapi/gssapi.h> OM_uint32 gss_unwrap(OM_uint32 *minor_status,
const gss_ctx_id_t context_handle,
const gss_buffer_t input_message_buffer,
gss_buffer_t output_message_buffer, int *conf_state,
gss_qop_t *qop_state);
The gss_unwrap() function converts a message previously protected by gss_wrap(3GSS) back to a usable form, verifying the embedded MIC. The conf_state parameter indicates whether the message was encrypted; the qop_state parameter indicates the strength of protection that was used to provide the confidentiality and integrity services.
Since some application-level protocols may wish to use tokens emitted by gss_wrap(3GSS) to provide secure framing, the GSS-API supports the wrapping and unwrapping of zero-length messages.
The parameter descriptions for gss_unwrap() follow:
minor_status
context_handle
input_message_buffer
output_message_buffer
conf_state
qop_state
gss_unwrap() may return the following status codes:
GSS_S_COMPLETE
GSS_S_DEFECTIVE_TOKEN
GSS_S_BAD_SIG
GSS_S_DUPLICATE_TOKEN
GSS_S_OLD_TOKEN
GSS_S_UNSEQ_TOKEN
GSS_S_GAP_TOKEN
GSS_S_CONTEXT_EXPIRED
GSS_S_NO_CONTEXT
GSS_S_FAILURE
See attributes(7) for descriptions of the following attributes:
ATTRIBUTE TYPE | ATTRIBUTE VALUE |
MT-Level | Safe |
gss_release_buffer(3GSS), gss_wrap(3GSS), attributes(7)
Solaris Security for Developers Guide
January 15, 2003 | OmniOS |