Hmmm... interesting. You'd think others would be having the same problem
on other platforms. I did a quick search and couldn't find anything that
stuck out. Personally, it sounds like IBM passing the buck again.

The fact that not everyone has this issue, and the ones that do trace and
get an odd date should be a major clue.

*shrug*





On Mon, Jun 7, 2021 at 8:59 AM Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx>
wrote:

reading back through my old case I had with IBM, they pointed out that the
successful client hello's had a similar ancient date in the random data,
and that it may just be a bug in wireshark that is throwing up the string
as a timestamp.

On Thu, Jun 3, 2021 at 7:34 PM Brad Stone <bvstone@xxxxxxxxx> wrote:

Yes, it was in the random data. They sent me a screenshot otherwise I'd
copy and paste it to an email.

On Thu, Jun 3, 2021 at 4:02 PM Gerald Magnuson <
gmagqcy.midrange@xxxxxxxxx

wrote:

was the old date and time from the client hello... in the Random
data?


On Thu, Jun 3, 2021 at 3:48 PM Gerald Magnuson <
gmagqcy.midrange@xxxxxxxxx

wrote:

I still have the wireshark trace, but I didn't flag the bad packet.
looking through it, I see lots of short hello's but the data/time
looks
right to me.



On Thu, Jun 3, 2021 at 3:18 PM Gerald Magnuson <
gmagqcy.midrange@xxxxxxxxx>
wrote:

I seem to recall that was the issue with us, that the packet that
wireshark flagged as in error (that IBM asked us to figure out why
it
was
bad)
had a bad date/time in it.



On Thu, Jun 3, 2021 at 7:48 AM Brad Stone <bvstone@xxxxxxxxx>
wrote:

But that timestamp comes from the IBM i and the time and date are
set
correctly. It's during the SSL negotiation. It doesn't always
send
it,
but when it does, it's from the wayback machine. Not sure how it's
getting
that date/time.

On Wed, Jun 2, 2021 at 4:46 PM Charles Wilt <
charles.wilt@xxxxxxxxx>
wrote:

That right there is probably your issue...

IIRC, SSL/TLS won't work unless the clocks on both sides are
correct...

Charles


On Wed, Jun 2, 2021 at 3:23 PM Brad Stone <bvstone@xxxxxxxxx>
wrote:

Ok, Thanks. I must have dreamt you posted a solution, or that
IBM
figured
it out.

What's weird in this case with a customer is when it happens it
sends
across a date and time that is in the 1980s during the client
hello.



On Wed, Jun 2, 2021 at 12:33 PM Gerald Magnuson <
gmagqcy.midrange@xxxxxxxxx>
wrote:

I have not found a solution as of yet.

I am on most current PTF levels, and problem is still
occurring.



On Wed, Jun 2, 2021 at 11:54 AM Brad Stone <
bvstone@xxxxxxxxx>
wrote:

I thought I had seen where Gerald or someone else had
posted
that IBM
finally figured out this SSL Handshake error with errno
415.

RC(415) Peer not recognized or badly formatted message
received.

I can't find it in the archives. Was that a dream? :)

Bradley V. Stone
www.bvstools.com
Native IBM i e-Mail solutions for Microsoft Office 365,
Gmail,
or any
Cloud
Provider!
--
This is the Web Enabling the IBM i (AS/400 and iSeries)
(WEB400)
mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.


--
This is the Web Enabling the IBM i (AS/400 and iSeries)
(WEB400)
mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.


--
This is the Web Enabling the IBM i (AS/400 and iSeries)
(WEB400)
mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.


--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 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.