Chapter 13. GT.CM Client/Server
 

In “Why do we need a $gtmcrypt_config file?”, gtmcrypt_config version 2

In “OpenSSL Options”, Default includes SSL_VERIFY_FAIL_IF_NO_PEER_CERT\nand additional configuration options

In “Database Upgrade Matrix”, replace V4 info

In “Usage”, Default is --devicedetail.

In “OpenSSL Options”, remove dh params

In “Why do we need a $gtmcrypt_config file?”, Eliminate dh512 and dh1024

In “Creating and signing demo leaf-level certificates”, no dh params

In “Why do we need a $gtmcrypt_config file?”, tlsids must begin with a letter.

In “Recommendations”, add recommendation for using restrictions to limit what facilities are available to GT.M applications

In “Philosophy”, add safety checks for system()

In “Building Encryption Libraries ”, AIX pre-reqs

In “Building Encryption Libraries ”, eliminate old platforms and reduce instruction bloat for linuxen

In “IBM AIX 7.1 (pSeries) ”, libgcrypt is an AIX requirement

In “Overview”, add information about the gtmpcat_for_{release} kit.

In “Usage”, add callin, cmdscript, gtmdeftypes, ppi, and regiondetail options.

In “Monitoring GT.M Messages”, improved the note on gtm_procstuckexec

In “GT.CM Client”, added clarity to the GT.CM client requirements

In “Introduction”, removed references to OpenVMS and move the cross-endian statement from the server section to this section.

In “Recommendations”, removed references to Solaris.

In “gtmsecshr Exception”, removed references to Solaris and HP-UX.

In “Managing core dumps ”, removed references to HP-UX and Solaris.

In “Overview”, removed references to HP-UX and Solaris.