× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


Thanks for your ideas.

I've tried searching the logs for a variety of things, including SSL and 1.0; no luck.

And I've been watching the connection counts and scanning the QAUDJRN around the time when a 1.0 connection was counted.

I just discovered the TLSCONFIG macro, so I've added

Option -netsecureTelnetServer:<enabled,disabled>
Determines if secure telnet handshakes should be audited
even if *NETTELSVR is not set in QAUDLVL or QAUDLVL2.
This field has no meaning if QAUDLVL or QAUDLVL2 does not
contain *NETSECURE. This field has no impact on what is
audited if QAUDLVL or QAUDLVL2 contains *NETTELSVR.

Option -display
SSL/TLS Connection Counters . . . . . : Enabled*
Netsecure Inspect Application Data . . : Allowed
Netsecure Telnet Server . . . . . . . : Enabled* < < < enabled

I'm waiting for a 1.0 connection to see if this adds more to the QAUDJRN.

--Paul E Musselman

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Thursday, July 14, 2022 3:43 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: TLSV1.x Usage in anticipation of v7.4

Would TLS1.0 appear in those journal entries as TLS1.0? Or might it appear as something else? For example, might it have thought of TLS1.0 still as SSL3.0?
What is DTLS?
Would a search for 1.0 be successful?
Can you check at the time when a known TLS1.0 connection may have made?

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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