gsk_secure_soc

Resets the session keys for a secure connection.

Format

   #include <gskssl.h>

   gsk_status gsk_secure_soc_reset(
                                    gsk_soc_data *     soc_handle)

Parameters

soc_handle: Specifies the connection handle returned by the gsk_secure_soc_init() routine.

Results

The function return value will be 0 (GSK_OK) if no error is detected. Otherwise, it will be one of the return codes listed in the gskssl.h include file. These are some possible errors:

[GSK_ERR_NO_NEGOTIATION]: An attempt was made to renegotiate a session when renegotiation is disabled.
[GSK_ERROR_BAD_MALLOC]: Insufficient storage is available.
[GSK_ERROR_BAD_SSL_HANDLE]: The connection handle is not valid.
[GSK_ERROR_CONNECTION_CLOSED]: The connection was closed by the peer application.
[GSK_ERROR_IO]: I/O error communicating with peer application.
[GSK_ERROR_NOT_SSLV3]: The session is not using the SSL V3 or TLS V1.0 protocol.
[GSK_ERROR_SOCKET_CLOSED]: Socket connection closed by peer application.

Usage

The gsk_secure_soc_reset() routine generates new session keys for the connection. A full SSL handshake will be performed if the session has expired. Otherwise a short SSL handshake will be performed. The gsk_secure_soc_reset() routine can be called only for a session using the SSL V3 or TLS V1.0 protocol. The gsk_secure_soc_reset() routine initiates the SSL handshake but does not wait for it to complete. Any pending handshake messages will be processed when the gsk_secure_soc_read() routine is called to process incoming data.

Format

Parameters

Results

Usage

Related Topics