Skip Navigation Links | |
Exit Print View | |
![]() |
Developer's Guide to Oracle Solaris Security Oracle Solaris 11 Express 11/10 |
1. Oracle Solaris Security for Developers (Overview)
2. Developing Privileged Applications
3. Writing PAM Applications and Services
4. Writing Applications That Use GSS-API
7. Writing Applications That Use SASL
8. Introduction to the Oracle Solaris Cryptographic Framework
9. Writing User-Level Cryptographic Applications and Providers
10. Introduction to the Oracle Solaris Key Management Framework
A. Sample C-Based GSS-API Programs
GSS-API Major Status Code Values
Address Types for Channel Bindings
Implementation-Specific Features in GSS-API
Implementations of Selected Data Types
Deletion of Contexts and Stored Data
Protection of Channel-Binding Information
Context Exportation and Interprocess Tokens
Types of Credentials Supported
Wrap Size Limits and QOP Values
Messages Returned in Kerberos v5 for Status Code 1
Messages Returned in Kerberos v5 for Status Code 2
Messages Returned in Kerberos v5 for Status Code 3
Messages Returned in Kerberos v5 for Status Code 4
Messages Returned in Kerberos v5 for Status Code 5
Messages Returned in Kerberos v5 for Status Code 6
Messages Returned in Kerberos v5 for Status Code 7
D. Source Code for SASL Example
The Oracle Solaris software implements the GSS-API functions. For more information on each function, see its man page. See also Functions From Previous Versions of GSS-API.
Assume a global identity by obtaining a GSS-API credential handle for preexisting credentials
Process a token on a security context from a peer application
Calculate a cryptographic message integrity code (MIC) for a message
Check a MIC against a message to verify integrity of a received message
Attach a MIC to a message, and optionally encrypt the message content
Verify a message with attached MIC. Decrypt message content if necessary
This section explains functions that were included in previous versions of the GSS-API.
The Sun implementation of GSS-API provides the following functions for convenience and for backward compatibility. However, these functions might not be supported by other implementations of GSS-API.
Although a mechanism's name can be converted from a string to an OID, programmers should use the default GSS-API mechanism if at all possible.
The following functions have been supplanted by newer functions. In each case, the new function is the functional equivalent of the older function. Although the old functions are supported, developers should replace these functions with the newer functions whenever possible.