System i: Programming Secure Sockets APIs - IBM
System i: Programming Secure Sockets APIs - IBM
System i: Programming Secure Sockets APIs - IBM
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
[GSK_ATTRIBUTE_INVALID_ID]<br />
The specified bufID was not valid.<br />
[GSK_INVALID_HANDLE]<br />
The specified handle was not valid.<br />
[GSK_AS400_ERROR_INVALID_POINTER]<br />
The buffer or bufSize pointer is not valid.<br />
[GSK_ERROR_UNSUPPORTED]<br />
The bufID currently is not supported.<br />
[GSK_ERROR_IO]<br />
An error occurred in SSL processing. Check the errno value.<br />
Error Conditions<br />
When the gsk_attribute_get_buffer() API fails with return code [GSK_ERROR_IO], errno can be set to:<br />
[EINTR] Interrupted function call.<br />
[EDEADLK] Resource deadlock avoided.<br />
[ETERM] Operation terminated.<br />
If an errno is returned that is not in this list, look in “Errno Values for UNIX-Type Functions” on page 103<br />
for a description of the errno.<br />
Usage Notes<br />
1. The following GSK_BUF_ID values may be retrieved from the SSL environment after<br />
gsk_environment_open().<br />
v GSK_KEYRING_FILE<br />
v GSK_KEYRING_PW<br />
v GSK_KEYRING_LABEL<br />
v GSK_OS400_APPLICATION_ID<br />
v GSK_V2_CIPHER_SPECS<br />
v GSK_V3_CIPHER_SPECS<br />
2. The following GSK_BUF_ID values may be retrieved from the secure session after<br />
gsk_secure_soc_open().<br />
v GSK_KEYRING_LABEL<br />
v GSK_V2_CIPHER_SPECS<br />
v GSK_V3_CIPHER_SPECS<br />
v GSK_CONNECT_SEC_TYPE<br />
v GSK_CONNECT_CIPHER_SPEC<br />
3. The following GSK_BUF_ID values are defaulted after gsk_secure_soc_open() and will be set for the<br />
secure session after gsk_secure_soc_init().<br />
v GSK_CONNECT_SEC_TYPE<br />
v GSK_CONNECT_CIPHER_SPEC<br />
v GSK_SID_VALUE<br />
4. The following GSK_BUF_ID values may be changed for the secure session after<br />
gsk_secure_soc_misc(), gsk_secure_soc_read() or gsk_secure_soc_startRecv() if an SSL Handshake<br />
happened under the context of those calls for the secure session.<br />
<strong>Secure</strong> <strong>Sockets</strong> <strong>APIs</strong> 5