Re: SSL/TLS 1.3 Handshake Error - Possible Fixes/PTFs RC(-11) RC(415)

Ok, IBM has me trying a different PTF.

On Mon, Feb 7, 2022 at 10:50 AM Brad Stone <bvstone@xxxxxxxxx> wrote:

If the PTF changed the cipher list, and you changed it back to what you
had, I don't doubt you're having the same problem. :)

ECDHE_RSA_AES_256_GCM_SHA384 and AES_256_GCM_SHA384 are both two that
IBM and myself personally identified as having problems, and they're both
in your list.

I think I see them in the list after the PTFs as well.

Who knows. The PTF specifics are pretty vague.


On Mon, Feb 7, 2022 at 10:13 AM Gerald Magnuson <
gmagqcy.midrange@xxxxxxxxx> wrote:

testing that ptf, MF69461.
I first changed my environment back to
QSSLCSLCTL = *USRDFN
and QSSLPCL is now set to TLS1.3;TLS1.2
and QSSLCSL is:
Sequence Cipher
number Suite
0
10 *ECDHE_RSA_AES_256_GCM_SHA384
20 *ECDHE_RSA_AES_128_GCM_SHA256
30 *RSA_AES_256_GCM_SHA384
40 *RSA_AES_128_GCM_SHA256
50 *AES_256_GCM_SHA384
60 *AES_128_GCM_SHA256


I am still getting the error.

On Wed, Feb 2, 2022 at 10:28 AM Gerald Magnuson <
gmagqcy.midrange@xxxxxxxxx>
wrote:

just over the weekend i applied a bunch of ptf groups, then the current
cumulative fixes, so there is a chance something else jacked with it.
the list is now:
Sequence Cipher
number Suite
0
10 *AES_128_GCM_SHA256
20 *AES_256_GCM_SHA384
30 *CHACHA20_POLY1305_SHA256
40 *ECDHE_ECDSA_AES_128_GCM_SHA256
50 *ECDHE_ECDSA_AES_256_GCM_SHA384
60 *ECDHE_RSA_AES_128_GCM_SHA256
70 *ECDHE_RSA_AES_256_GCM_SHA384
80 *ECDHE_ECDSA_CHACHA20_POLY1305_SHA256
90 *ECDHE_RSA_CHACHA20_POLY1305_SHA256