|
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
On Wed, Feb 2, 2022 at 10:18 AM Brad Stone <bvstone@xxxxxxxxx> wrote:
So the PTF changed system values and probably removed certain ciphers? I
hope there's more to it than that.
On Wed, Feb 2, 2022 at 10:10 AM Gerald Magnuson <
gmagqcy.midrange@xxxxxxxxx>
wrote:
I put the fix on my DR machine.it.
ARGH! I should have looked at my QSSL* system values before I applied
QSSLCSLCTL and QSSLPCL is now set to *OPSYS (should be *USRDFN, andthem:
TLS1.3;TLS1.2)
and QSSLCSL is different from my production.
On Tue, Feb 1, 2022 at 6:53 PM Brad Stone <bvstone@xxxxxxxxx> wrote:
I know so far this has only affected a few of us so far, but I had a
customer report that IBM has issued PTFs that solved the issue for
For
V7R3: https://www.ibm.com/support/pages/ptf/MF69465
V7R4: https://www.ibm.com/support/pages/ptf/MF69461
The errors in question are:
Error performing SSL Handshake. RC(-11) or RC(-16) PeerCertRC(0) -
theGSKit
base IBM SSL APIs
Error performing SSL handshake. RC(415) errno(0) - When using the
relatedSSL APIsCloud
Also updated on my FieldExit.com post:
https://fieldexit.com/forum/display?threadid=618
I'm not sure what they do.. hopefully it's not just removing certain
ciphers from the active list.
Bradley V. Stone
www.bvstools.com
Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or any
Provider!list
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
affiliatequestions.
Help support midrange.com by shopping at amazon.com with our
listlink: https://amazon.midrange.com--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxxrelated
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
questions.--
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.