System i: Programming Secure Sockets APIs - IBM

More documents

Recommendations

Info

Error Messages Message ID Error Message Text CPE3418 E Possible APAR condition or hardware failure. CPF9872 E Program or service program &1 in library &2 ended. Reason code &3. CPFA081 E Unable to set return value or error code. Usage Notes 1. The SSL_Write() function is only valid on sockets that have an address family of AF_INET or AF_INET6 and a socket type of SOCK_STREAM. If the descriptor pointed to by the handle structure parameter does not have the correct address family and socket type, [SSL_ERROR_IO] is returned and the errno value is set to EINVAL. 2. There is no maximum length of the data that can be written. However, SSL will segment the data into multiple SSL record buffers if it will not fit in one SSL record buffer. The maximum SSL record size is 32 KB minus the necessary SSL record headers. 3. If the createFlags field in the SSLHandle specifies a value that does not include the SSL_ENCRYPT flag, then this function will simply call the sockets write() function. 4. Unpredictable results will occur when attempting to mix calls to SSL_Write() and any of the sockets write functions (send(), write(), writev(), and so forth). It is strongly suggested that you do not mix the SSL_Write() API with any of the sockets write functions. Related Information 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_Read()—Receive Data from an SSL-Enabled Socket Descriptor” on page 91—Receive Data from an SSL-Enabled Socket Descriptor API introduced: V4R3 Concepts These are the concepts for this category. Top | UNIX-Type APIs | APIs by category Header Files for UNIX-Type Functions Programs using the UNIX ® -type functions must include one or more header files that contain information needed by the functions, such as: v Macro definitions v Data type definitions v Structure definitions v Function prototypes 100 System i: Programming Secure Sockets APIs
The header files are provided in the QSYSINC library, which is optionally installable. Make sure QSYSINC is on your system before compiling programs that use these header files. For information about installing the QSYSINC library, see Include files and the QSYSINC library. The table below shows the file and member name in the QSYSINC library for each header file used by the UNIX-type APIs in this publication. Name of Header File Name of File in QSYSINC Name of Member arpa/inet.h ARPA INET arpa/nameser.h ARPA NAMESER bse.h H BSE bsedos.h H BSEDOS bseerr.h H BSEERR dirent.h H DIRENT errno.h H ERRNO fcntl.h H FCNTL grp.h H GRP inttypes.h H INTTYPES limits.h H LIMITS netdbh.h H NETDB netinet/icmp6.h NETINET ICMP6 net/if.h NET IF netinet/in.h NETINET IN netinet/ip_icmp.h NETINET IP_ICMP netinet/ip.h NETINET IP netinet/ip6.h NETINET IP6 netinet/tcp.h NETINET TCP netinet/udp.h NETINET UDP netns/idp.h NETNS IDP netns/ipx.h NETNS IPX netns/ns.h NETNS NS netns/sp.h NETNS SP net/route.h NET ROUTE nettel/tel.h NETTEL TEL os2.h H OS2 os2def.h H OS2DEF pwd.h H PWD Qlg.h H QLG qp0lchsg.h H QP0LCHSG qp0lflop.h H QP0LFLOP qp0ljrnl.h H QP0LJRNL qp0lror.h H QP0LROR qp0lrro.h H QP0LRRO qp0lrtsg.h H QP0LRTSG Secure Sockets APIs 101
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 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?