1,126
edits
Difference between revisions of "IBM Content Manager OnDemand v10.5.0.7 and GSKit support for Post-Quantum Cryptography"
IBM Content Manager OnDemand v10.5.0.7 and GSKit support for Post-Quantum Cryptography (view source)
Revision as of 22:35, 27 March 2024
, 22:35, 27 March 2024Added troubleshooting item rc 407 GSK_ERROR_BAD_KEYFILE_LABEL .
(IBM CMOD v10.5 and GSKit v8.0.55 breaks SSL/TLS.) |
(Added troubleshooting item rc 407 GSK_ERROR_BAD_KEYFILE_LABEL .) |
||
| Line 35: | Line 35: | ||
: Using the <code> arssockd -I ARCHIVE -p</code> option when <code> SSL_USECLNT_SSL=1</code> is set in [[ars.ini]] results in a failed connection. | : Using the <code> arssockd -I ARCHIVE -p</code> option when <code> SSL_USECLNT_SSL=1</code> is set in [[ars.ini]] results in a failed connection. | ||
: Checking your KeyDB with <code> gsk8capicmd_64 -cert -verify</code> produces 'OK'. | : Checking your KeyDB with <code> gsk8capicmd_64 -cert -verify</code> produces 'OK'. | ||
: If you run a server trace on arssockd, you will find a return code 407 from GSKit also known as <code>GSK_ERROR_BAD_KEYFILE_LABEL</code>. | |||
== Solution == | == Solution == | ||