AT-TLS uses System SSL. With trace turned on, then I get the following at startup crypto_init(): Crypto assist supports strong encryption crypto_init(): FIPS mode level 1101 crypto_init(): SHA-1 crypto assist is available crypto_init(): SHA-224 crypto assist is available crypto_init(): SHA-256 crypto assist is available crypto_init(): SHA-384 crypto assist is available crypto_init(): SHA-512 crypto assist is available crypto_init(): DES crypto assist is available crypto_init(): DES3 crypto assist is available crypto_init(): AES 128-bit crypto assist is available crypto_init(): AES 256-bit crypto assist is available crypto_init(): AES-GCM crypto assist is available
*crypto_init(): Cryptographic accelerator is not available crypto_init(): Cryptographic coprocessor is available * crypto_init(): Public key hardware support is available In the environment file for my system ssl application I have GSK_TRACE_FILE=/tmp/zzztrace.file GSK_TRACE=0x0f and format it using gsktrace /tmp/zzztrace.file >> aa Colin On Tue, 9 Jul 2024 at 05:37, Jake Anderson < [email protected]> wrote: > Hello > > Cross Posted > > Is there a way to know if the ATTLS communication are using the CRYPTO CARD > ? > > Any procedure to trace to understand? > > Jake > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
