Re: Bad Peer (415) SSL Handshake Error update

Well, I told the tech that this isn't a fix, and if they want help being
able to recreate the problem on their system, I am happy to provide license
keys for GETURI and a sample command to run. Super simple to do.

I am surprised they aren't seeing it on their client applications such as
email, SQL HTTP calls, etc. Maybe they are but they just loop around them
too. haha.

On Tue, Oct 5, 2021 at 4:10 PM Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx>
wrote:

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... we
shall see if my stuff starts breaking.

That's why I said it is a "fix", not a real fix. Something is wrong

with

GSKit and TLS 1.3 if this solves the issue. I'm not going to start

telling

my customers to disable TLS 1.3 to fix the issue... lol!

On Tue, Oct 5, 2021 at 3:54 PM Gerald Magnuson <

gmagqcy.midrange@xxxxxxxxx

wrote:

I can't remove TLS1.3,
our company is of the viewpoint that anything less than that is a

security

issue.



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

the

same SSL "hello" would work, and then another (that they claim is the

exact

same... I don't know.. I can't read those traces! haha) the server

returned

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

have

one

big backup jog that runs at night that I am running now to see if

that

happens, 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

any

errors and retry until it's successful. So if that log comes back

clean,

and 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

sites

were updating their SSL certificates.

I must say this... after actually getting in touch with someone at

IBM

I

am

very happy and surprised with the service.. I expected this to go on

for

days.

Bradley V. Stone
www.bvstools.com
Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or any

Cloud

Provider!
--
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

--
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

--
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

--
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