System i: Programming Secure Sockets APIs - IBM

More documents

Recommendations

Info

struct SSLHandleStr { /* SSLHandleStr */ int fd; /* Socket descriptor */ int createFlags; /* SSL_Create flags value */ unsigned protocol; /* SSL protocol version */ unsigned timeout; /* Timeout value in seconds */ unsigned char cipherKind[3]; /* Current 2.0 cipher suite*/ unsigned short int cipherSuite; /* Current 3.0 cipher suite */ unsigned short int* cipherSuiteList; /* List of cipher suites */ unsigned int cipherSuiteListLen; /* Number of entries in the cipher suites list */ unsigned char* peerCert; /* Peer certificate */ unsigned peerCertLen; /* Peer certificate length */ int peerCertValidateRc; /* Return code from validation of certficate */ int (*exitPgm)(struct SSLHandleStr* sslh); /* Authentication exit program called when a certificate is received during SSL handshake */ }; void *buffer (input) A pointer to the user-supplied buffer in which the data to be written is stored. int buffer_length (input) The length of the buffer. Authorities No authorization is required. Return Value SSL_Write() returns an integer. Possible values are: [n] Successful, where n is the number of bytes written. [SSL_ERROR_BAD_STATE] SSL detected a bad state in the SSL session. [SSL_ERROR_CLOSED] The SSL session ended. [SSL_ERROR_IO] An error occurred in SSL processing; check the errno value. [SSL_ERROR_UNKNOWN] An unknown or unexpected error occurred during SSL processing. Error Conditions When the SSL_Write() API fails with return code [SSL_ERROR_IO], errno can be set to to one of the following: [EBADF] [EFAULT] Descriptor not valid. 98 System i: Programming Secure Sockets APIs
Bad address. One of the following conditions occurred: v The system detected an address that was not valid while attempting to access the buffer parameter. v The system detected an address that was not valid while attempting to access the handle parameter or one of the address fields in the handle parameter. [EINTR] [EINVAL] [EIO] [ENOBUFS] [ENOTCONN] Interrupted function call. Parameter not valid. This error code indicates one of the following: v The socket_descriptor type is not SOCK_STREAM or address family is not AF_INET or AF_INET6. v One of the parameters passed is not valid or is NULL. v The buffer_length parameter specifies a negative value. Input/output error. There is not enough buffer space for the requested operation. Requested operation requires a connection. This error code indicates one of the following: v The socket_descriptor is not for a socket that is in a connected state. v The socket_descriptor has not had SSL support enabled. This usually means that an SSL_Create() has not been completed for this socket_descriptor. [ENOTSOCK] [EPIPE] The specified descriptor does not reference a socket. Broken pipe. [ETIMEDOUT] [EUNATCH] [EUNKNOWN] A remote host did not respond within the timeout period. The protocol required to support the specified address family is not available at this time. Unknown system state. [EWOULDBLOCK] Operation would have caused the thread to be suspended. Secure Sockets APIs 99
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 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 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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?