System i: Programming Secure Sockets APIs - IBM

More documents

Recommendations

Info

6. Socket option SO_SNDTIMEO is not supported by this API. Semantics similar to SO_SNDTIMEO can be obtained using the operationWaitTime field in the Qso_OverLappedIO_t structure. Related Information v “gsk_secure_soc_init()—Negotiate a secure session” on page 38—Negotiate a secure session v “gsk_secure_soc_misc()—Perform miscellaneous functions for a secure session” on page 41—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_startRecv()—Start asynchronous receive operation on a secure session” on page 52—Start Asynchronous Receive Operation on a secure session v QsoCancelOperation()—Cancel an I/O Operation v QsoPostIOCompletionPort()—Post Request on I/O Completion Port v QsoCreateIOCompletionPort()—Create I/O Completion Port v QsoDestroyIOCompletionPort()—Destroy I/O Completion Port v QsoStartRecv—Start Asynchronous Recv Operation v QsoStartSend—Start Asynchronous Send Operation v QsoWaitForIOCompletion()—Wait for I/O Completion Operation v send()—Send Data API introduced: V5R1 Top | UNIX-Type APIs | APIs by category gsk_secure_soc_write()—Send data on a secure session Syntax #include int gsk_secure_soc_write(gsk_handle my_session_handle, char *writeBuffer, int writeBufSize, int *amtWritten); Service Program Name: QSYS/QSOSSLSR Default Public Authority: *USE Threadsafe: Yes The gsk_secure_soc_write() function is used by a program to write data on a secure session. Parameters my_session_handle (Input) The handle, returned from gsk_secure_soc_open() and used on the gsk_secure_soc_init() API call that initialized the secure session over which data is to be written. 60 System i: Programming Secure Sockets APIs
writeBuffer (Input) The pointer to the user-supplied buffer from which the data is to be written. writeBufSize (Input) The number of bytes to be written. amtWritten (Output) The number of bytes written as a result of this API call. Authorities No authorization is required. Return Value gsk_secure_soc_write() returns an integer. Possible values are: [GSK_OK] gsk_secure_soc_write() was successful. [GSK_INVALID_HANDLE] The handle specified was not valid. [GSK_INVALID_STATE] The handle is not in the correct state for this operation. [GSK_INVALID_BUFFER_SIZE] The readBufSize is less than 1. [GSK_WOULD_BLOCK] Operation would have caused the process to be suspended. [GSK_ERROR_SOCKET_CLOSED] A close() was done on the socket descriptor for this secure session. [GSK_AS400_ERROR_CLOSED] The secure session was closed by another thread before the write completed. [GSK_AS400_ERROR_INVALID_POINTER] The writeBuffer or amtWritten pointer is not valid. [GSK_INTERNAL_ERROR] An unexpected error occurred during SSL processing. [GSK_ERROR_IO] An error occurred in SSL processing; check the errno value. Error Conditions When the gsk_secure_soc_write() API fails with return code [GSK_ERROR_IO], errno can be set to: [EIO] [ENOTCONN] [ENOTSOCK] Input/output error. Requested operation requires a connection. Secure Sockets APIs 61
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 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 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 98 and 99: Parameters int sslreturnvalue (Inpu
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 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?