System i: Programming Secure Sockets APIs - IBM

More documents

Recommendations

Info

[GSK_INVALID_STATE] One of the following occurred: v bufID cannot be set for a SSL environment after a gsk_environment_init() has been issued. v bufID cannot be set for a secure session after a gsk_secure_soc_init() has been issued. [GSK_ERROR_UNSUPPORTED] The bufID value is currently not supported. [GSK_INSUFFICIENT_STORAGE] Not able to allocate storage for the requested operation. [GSK_ERROR_IO] An error occurred in SSL processing, check the errno value. Error Conditions When the gsk_attribute_set_buffer() API fails with return code [GSK_ERROR_IO], errno can be set to: [EINTR] Interrupted function call. [EDEADLK] Resource deadlock avoided. [ETERM] Operation terminated. If an errno is returned that is not in this list, look in “Errno Values for UNIX-Type Functions” on page 103 for a description of the errno. Usage Notes 1. The following GSK_BUF_ID values may be set in the SSL environment after gsk_environment_open() and before gsk_environment_init(). They are used as defaults for subsequent secure sessions: v GSK_KEYRING_FILE v GSK_KEYRING_PW v GSK_KEYRING_LABEL v GSK_OS400_APPLICATION_ID v GSK_V2_CIPHER_SPECS v GSK_V3_CIPHER_SPECS 2. The following GSK_BUF_ID values may be set for each individual secure session after gsk_secure_soc_open() and before gsk_secure_soc_init(). These values will override values set in the SSL environment: v GSK_KEYRING_LABEL v GSK_V2_CIPHER_SPECS v GSK_V3_CIPHER_SPECS 3. The following GSK_V3_CIPHER_SPECS values are the SSL Version 3 ciphers and the TLS Version 1 ciphers supported when the operating system is installed: 01 = *RSA_NULL_MD5 02 = *RSA_NULL_SHA 03 = *RSA_EXPORT_RC4_40_MD5 04 = *RSA_RC4_128_MD5 05 = *RSA_RC4_128_SHA 06 = *RSA_EXPORT_RC2_CBC_40_MD5 18 System i: Programming Secure Sockets APIs
09 = *RSA_DES_CBC_SHA 0A = *RSA_3DES_EDE_CBC_SHA 2F = *RSA_AES_128_CBC_SHA (TLS Version 1 only) 35 = *RSA_AES_256_CBC_SHA (TLS Version 1 only) NULL = Default cipher specs are used (may change in future) The default list is ’2F0504350A’ 4. SSL Version 2 support is disabled when the operating system is installed resulting in no SSL Version 2 ciphers being supported. If SSL Version 2 is enabled (not recommended), the following GSK_V2_CIPHER_SPECS values are the SSL Version 2 ciphers that would be supported if shipped supported cipher list has not been altered. 1 = *RSA_RC4_128_MD5 2 = *RSA_EXPORT_RC4_40_MD5 4 = *RSA_EXPORT_RC2_CBC_40_MD5 NULL = Default cipher specs are used (may change in future) The default list is ’1’ The following GSK_V2_CIPHER_SPECS values are the SSL Version 2 ciphers potentially supported if an administrator later enables SSL Version 2: 1 = *RSA_RC4_128_MD5 2 = *RSA_EXPORT_RC4_40_MD5 3 = *RSA_RC2_CBC_128_MD5 4 = *RSA_EXPORT_RC2_CBC_40_MD5 6 = *RSA_DES_CBC_MD5 7 = *RSA_3DES_EDE_CBC_MD5 NULL = Default cipher specs are used (may change in future) The default list is ’136’ 5. The list of supported cipher suites and the ordered list of default cipher suites are configurable from the Change System Value (CHGSYSVAL) command. The Display System Value (DSPSYSVAL) command or the Retrieve System Values (QWCRSVAL) API can be used to determine the current settings of the supported ciphers (QSSLCSL) and protocols (QSSLPCL) for system SSL. 6. The following GSK_BUF_ID values currently are not supported in the i5/OS ® implementation: v GSK_KEYRING_STASH_FILE v GSK_LDAP_SERVER v GSK_LDAP_USER v GSK_LDAP_USER_PW v GSK_USER_DATA v GSK_SID_VALUE v GSK_PKCS11_DRIVER_PATH v GSK_PKCS11_TOKEN_LABEL v GSK_PKCS11_TOKEN_PWD v GSK_CSP_NAME 7. The following are the possible scenerios for the use of GSK_KEYRING_LABEL: v GSK_KEYRING_LABEL can be set after gsk_environment_open() and before gsk_environment_init() to indicate which certificate in the GSK_KEYRING_FILE to use for the secure environment. v GSK_KEYRING_LABEL can be set after gsk_secure_soc_open() and before gsk_secure_soc_init() to indicate which certificate in the GSK_KEYRING_FILE to use for the secure session. v If GSK_KEYRING_LABEL is not set, the default certificate label in the GSK_KEYRING_FILE is used for the SSL environment. Secure Sockets APIs 19
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 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 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?