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



Justin, for how long are you assigning the cert for.

https://www.ibm.com/support/pages/configuring-ssl-telnet-and-host-servers-server-authentication-first-time



On Tue, Apr 28, 2020 at 2:20 PM <midrangel@xxxxxxxxxxxxxxxxx> wrote:

Yes they will. Remember not to make the same mistake I just made a few
days
ago. You must authorize all the host servers to the certificate as well as
the telnet server. Once you have that going then you can change the telnet
attributes to only listen on 992 if that's what you want.

--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Justin
Taylor
Sent: Tuesday, April 28, 2020 1:18 PM
To: MIDRANGE-L (midrange-l@xxxxxxxxxxxxxxxxxx)
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Allow SSL for 5250

I'm planning the process of allowing SSL for 5250, and I'd really
appreciate
feedback to make sure I'm doing this correctly. I really, really need to
avoid breaking all of 5250.

My TELNET Properties show:
Socket layer support to be started with server:
Both secure and non-secure

DCM shows:
IBM i TCP/IP Telnet Server None assigned


First I'm going to assign my cert in DCM and bounce telnet. This will have
no apparent effect. Then in my ACS, I'll check the "Use SSL for
connection"
and my 5250 will be encrypted and show the closed lock. Existing 5250
sessions will continue to operate unencrypted with no disruption at all.

Is that about it?


TIA

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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.