|
The problem in that we pass hello's 100 times to the same pier as TLS1.3,
but then suddenly
it appears to try to handshake as TLS1.2 or TLS1.1 is what is so very
strange to me.
___AND____ 98% of these errors occur between 8am and 11am. However,
this is only about 60% of our traffic.
On Tue, Oct 5, 2021 at 3:57 PM Brad Stone <bvstone@xxxxxxxxx> wrote:
Well, I just hope it doesn't affect anything else I have running... wewith
shall see if my stuff starts breaking.
That's why I said it is a "fix", not a real fix. Something is wrong
GSKit and TLS 1.3 if this solves the issue. I'm not going to starttelling
my customers to disable TLS 1.3 to fix the issue... lol!gmagqcy.midrange@xxxxxxxxx
On Tue, Oct 5, 2021 at 3:54 PM Gerald Magnuson <
havewrote:
I can't remove TLS1.3,security
our company is of the viewpoint that anything less than that is a
issue.the
On Tue, Oct 5, 2021 at 3:48 PM Brad Stone <bvstone@xxxxxxxxx> wrote:
Well, I worked with IBM and got them a trace. They found it odd that
same SSL "hello" would work, and then another (that they claim is theexact
same... I don't know.. I can't read those traces! haha) the serverreturned
an "Illegal Parameter" error.
They had me go into SST and remove TLS 1.3 and also from QSSLPCL.
I have run my test a few times and received zero errors so far. I
thatone
big backup jog that runs at night that I am running now to see if
anyhappens, as it does many GETURI calls to Google Drive and OneDrive to
upload my backups. I updated the log a couple months ago to report
IBMclean,errors and retry until it's successful. So if that log comes back
sitesand so does tomorrow morning's log, then I'd call it "fixed". But not
really "fixed". :)
I think the clue was I said it just started happening recently when
were updating their SSL certificates.
I must say this... after actually getting in touch with someone at
Imailing
amfor
very happy and surprised with the service.. I expected this to go on
days.Cloud
Bradley V. Stone
www.bvstools.com
Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or any
Provider!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
affiliatelistrelated
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
questions.
Help support midrange.com by shopping at amazon.com with our
relatedlistlink: https://amazon.midrange.com--
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
listquestions.--
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
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
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-2024 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.