System i: Programming Secure Sockets APIs - IBM

v “gsk_attribute_set_enum()—Set enumerated information for a secure session or an SSL environment”
on page 24—Set enumerated information for a secure session or an SSL environment.
v “gsk_attribute_set_numeric_value()—Set numeric information for a secure session or an SSL
environment” on page 28—Set numeric information for a secure session or an SSL environment
v “gsk_secure_soc_close()—Close a secure session” on page 37—Close a secure session
v “gsk_secure_soc_misc()—Perform miscellaneous functions for a secure session”—Perform miscellaneous
functions for a secure session
v “gsk_secure_soc_open()—Get a handle for a secure session” on page 44—Get a handle for a secure
session
v “gsk_secure_soc_read()—Receive data on a secure session” on page 46—Receive data on a secure
session
v “gsk_secure_soc_startInit()—Start asynchronous operation to negotiate a secure session” on page
48—Start asynchronous operation to negotiate a secure session
v “gsk_secure_soc_write()—Send data on a secure session” on page 60—Send data on a secure session
v “gsk_strerror()—Retrieve GSKit runtime error message” on page 62—Retrieve GSK runtime error
message
API Introduced: V5R1
Top | UNIX-Type APIs | APIs by category
gsk_secure_soc_misc()—Perform miscellaneous functions for a secure
session
Syntax
#include
int gsk_secure_soc_misc(gsk_handle my_session_handle,
GSK_MISC_ID miscID);
Service Program Name: QSYS/QSOSSLSR
Default Public Authority: *USE
Threadsafe: Yes
The gsk_secure_soc_misc() function is used to perform miscellaneous functions for a secure session.
Parameters
my_session_handle (Input)
The handle for the secure session obtained from gsk_secure_soc_open() and after performing a
gsk_secure_soc_init().
miscID (Input)
One of the following operations:
v GSK_RESET_CIPHER (100) - Performs another SSL handshake for the SSL session identified
by the my_session_handle parameter. If an SSL session’s cache entry is still valid and both end
points of the SSL session allow using a cache entry, an abbreviated SSL handshake may be
performed. If the SSL cache entry for this session has expired or if the SSL session’s cache entry
has been reset with the GSK_RESET_SESSION function, or if one end point of the SSL session
does not allow using the SSL session cache entry, then a full SSL handshake will be performed.
v GSK_RESET_SESSION (101) - Removes this set of SSL session attributes from the SSL session
cache. Any new SSL session handshake requests to the peer end point will not use this set of
Secure Sockets APIs 41