System i: Programming Secure Sockets APIs - IBM

More documents

Recommendations

Info

Parameters int sslreturnvalue (Input) The Return Value received from a SSL API. char* string (Input) The string to be printed prior to the message associated with the sslreturnvalue. If no preceding message is desired, NULL must be entered. Authorities No authorization is required. Return Value There is no return value. Error Conditions This API calls the Retrieve SSL Runtime Error Message (SSL_Strerror) API in order to perform its task. It inherits all error conditions from this function. If the sslreturnvalue is unrecognized or if unable to retrieve the message corresponding to sslreturnvalue, then an Unknown error message will be printed following the string. Also, the message associated with the value found in the thread’s errno is printed. Note: the value of errno may be updated by SSL_Perror() in some error conditions. Error Messages See Error Conditions. Related Information v “SSL_Strerror()—Retrieve SSL Runtime Error Message” on page 95—Retrieve SSL Runtime Error Message v “SSL_Create()—Enable SSL Support for the Specified Socket Descriptor” on page 69—Enable SSL Support for the Specified Socket Descriptor v “SSL_Destroy()—End SSL Support for the Specified SSL Session” on page 71—End SSL Support for the Specified SSL Session v “SSL_Handshake()—Initiate the SSL Handshake Protocol” on page 74—Initiate the SSL Handshake Protocol v “SSL_Init()—Initialize the Current Job for SSL” on page 80—Initialize the Current Job for SSL v “SSL_Init_Application()—Initialize the Current Job for SSL Processing Based on the Application Identifier” on page 84—Initialize the Current Job for SSL Processing Based on the Application Identifier v “SSL_Read()—Receive Data from an SSL-Enabled Socket Descriptor” on page 91—Receive Data from an SSL-Enabled Socket Descriptor v “SSL_Write()—Write Data to an SSL-Enabled Socket Descriptor” on page 97—Write Data to an SSL-Enabled Socket Descriptor Example The following example shows how SSL_Perror() is used. Note: By using the code examples, you agree to the terms of the “Code license and disclaimer information” on page 111. #include #include #include #include #include 90 System i: Programming Secure Sockets APIs
#include #include /* bufferLen is 250 bytes */ #define bufferLen 250 void main() { int bufferLen, on = 1, rc = 0, sd, sd2, addrlen = 0; char buffer[bufferLen]; } SSLInit sslinit; SSLHandle* sslh; struct sockaddr_in addr; unsigned short int cipher[3] = { SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5 }; /*************************************************/ /* memset sslinit structure to hex zeros and */ /* fill in values for the sslinit structure */ /*************************************************/ memset((char *)&SSL_Init, 0x00, sizeof(sslinit)); sslinit.keyringFileName = "/keyringfile.kyr"; sslinit.keyringPassword = NULL; sslinit.cipherSuiteList = &cipher[0]; sslinit.cipherSuiteListLen = 3; /*************************************************/ /* initialize SSL security call SSL_Init */ /*************************************************/ if ((rc = SSL_Init(&sslinit)) != 0) { SSL_Perror(rc, "Could not initialize SSL"); } ... API introduced: V5R1 Top | UNIX-Type APIs | APIs by category SSL_Read()—Receive Data from an SSL-Enabled Socket Descriptor Syntax #include int SSL_Read(SSLHandle *handle, void *buffer, int buffer_length) Service Program Name: QSOSSLSR Default Public Authority: *USE Threadsafe: Yes The SSL_Read() function is used by a program to receive data from an SSL-enabled socket descriptor. Secure Sockets APIs 91
Page 1:
System i Programming Secure Sockets
Page 4 and 5:
Note Before using this information
Page 6 and 7:
Related Information . . . . . . . .
Page 8 and 9:
vi System i: Programming Secure Soc
Page 10 and 11:
APIs These are the APIs for this ca
Page 12 and 13:
ufID (Input) The following values c
Page 14 and 15:
v GSK_CONNECT_CIPHER_SPEC v GSK_SID
Page 16 and 17:
[GSK_INSUFFICIENT_STORAGE] Not able
Page 18 and 19:
gsk_attribute_get_enum()—Get enum
Page 20 and 21:
secure session does not start, and
Page 22 and 23:
API introduced: V5R1 Top | UNIX-Typ
Page 24 and 25:
v GSK_FD v GSK_HANDSHAKE_TIMEOUT v
Page 26 and 27:
[GSK_INVALID_STATE] One of the foll
Page 28 and 29:
8. If GSK_OS400_APPLICATION_ID is s
Page 30 and 31:
if validation fails because the cer
Page 32 and 33:
gsk_attribute_set_enum()—Set enum
Page 34 and 35:
active secure sessions will continu
Page 36 and 37:
gsk_attribute_set_numeric_value()
Page 38 and 39:
v GSK_V3_SIDCACHE_SIZE v GSK_LDAP_S
Page 40 and 41:
v “gsk_secure_soc_init()—Negoti
Page 42 and 43:
[ETERM] Operation terminated. If an
Page 44 and 45:
2. v GSK_SESSION_TYPE set to GSK_CL
Page 46 and 47:
Error Messages Message ID Error Mes
Page 48 and 49: [GSK_AS400_ERROR_INVALID_POINTER] T
Page 50 and 51: attributes. In most cases, as resul
Page 52 and 53: Error Messages Message ID Error Mes
Page 54 and 55: v “gsk_secure_soc_misc()—Perfor
Page 56 and 57: matched sets. If a client applicati
Page 58 and 59: Authorities Authorization of *R (al
Page 60 and 61: gsk_secure_soc_startRecv()—Start
Page 62 and 63: The handle specified was not valid.
Page 64 and 65: v “gsk_secure_soc_misc()—Perfor
Page 66 and 67: Authorities No authorization is req
Page 68 and 69: 6. Socket option SO_SNDTIMEO is not
Page 70 and 71: [EPIPE] [EUNATCH] The specified des
Page 72 and 73: Example The following example shows
Page 74 and 75: Qlg_Path_Name_T *keyringFileName (i
Page 76 and 77: v The CCSID specified in the keyrin
Page 78 and 79: unsigned protocol; /* SSL protocol
Page 80 and 81: Service Program Name: QSOSSLSR Defa
Page 82 and 83: Related Information v “SSL_Create
Page 84 and 85: unsigned int cipherSuiteListLen The
Page 86 and 87: [EBADF] [EBUSY] Permission denied.
Page 88 and 89: ignore attempts by applications to
Page 90 and 91: C Constant System Value TLS_RSA_WIT
Page 92 and 93: ignore attempts by applications to
Page 94 and 95: v Use the system default cipher spe
Page 96 and 97: An error occurred in SSL processing
Page 100 and 101: Parameters SSLHandle* handle (input
Page 102 and 103: [EUNATCH] [EUNKNOWN] The protocol r
Page 104 and 105: Authorities No authorization is req
Page 106 and 107: struct SSLHandleStr { /* SSLHandleS
Page 108 and 109: Error Messages Message ID Error Mes
Page 110 and 111: Name of Header File Name of File in
Page 112 and 113: Name Value Text Details ENOTWRITE 3
Page 114 and 115: Name Value Text Details EHOSTDOWN 3
Page 116 and 117: Name Value Text Details EISDIR 3471
Page 118 and 119: Name Value Text Details EBADFID 351
Page 120 and 121: CONDITIONS OF MERCHANTABILITY, FITN
Page 122 and 123: IBM Corporation Software Interopera
Page 124 and 125: SAA SecureWay SOM System i System i
Page 126: 118 System i: Programming Secure So
show all

System i: Programming Secure Sockets APIs - IBM

Create successful ePaper yourself

Delete template?

Save as template?