RE: TLSV1.x Usage in anticipation of v7.4

Yes, once I added TLSCONFIG I was able to see the V1.0 transactions, and the audit log does include the IP address.

It's part of the TELNET links; we're investigating to see what's going on. Appears to be within our network. Possibly printers.



_________________________________________________
If you have a support issue, please Submit a ServiceNow Ticket

Paul E Musselman
Sr. Technical Support Analyst
IT Power Systems
North America Information Technology

Cell + 1 859 953 3134
Email: paul.musselman@xxxxxxxxxxxxxxxxx
4 Tesseneer Drive
Highland Heights, KY 41076
United States



-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Friday, July 15, 2022 7:53 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: TLSV1.x Usage in anticipation of v7.4

Did the audit display the IP number? If so it should be really easy to track down.

SELECT JOB_NAME, AUTHORIZATION_NAME, CLIENT_IP_ADDRESS
FROM TABLE (QSYS2.ACTIVE_JOB_INFO(DETAILED_INFO=>'ALL')) X
WHERE CLIENT_IP_ADDRESS = '10.14.9.22'
;

If you have elevated authority you can even do this:
SELECT JOB_NAME, x.AUTHORIZATION_NAME, CLIENT_IP_ADDRESS, text_description
FROM TABLE (QSYS2.ACTIVE_JOB_INFO(DETAILED_INFO=>'ALL')) X
left outer join qsys2.user_info_basic u on x.authorization_name = u.authorization_name
WHERE CLIENT_IP_ADDRESS = '10.14.9.22'
;

If you don't have elevated authority this will do much the same.
SELECT JOB_NAME, x.AUTHORIZATION_NAME, CLIENT_IP_ADDRESS, OBJTEXT
FROM TABLE (QSYS2.ACTIVE_JOB_INFO(DETAILED_INFO=>'ALL')) X
left outer join table(qsys2.object_statistics('QUSRSYS', '*MSGQ')) u on x.authorization_name = u.OBJNAME
WHERE CLIENT_IP_ADDRESS = '10.14.9.22'
;

Rob Berendt