× 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 Scott. Exactly what I was looking for. I somehow missed the *ONLY option.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Monday, November 10, 2008 1:18 PM
To: Midrange Systems Technical Discussion
Subject: Re: Allowing only secure telnet

Hi Mike,

We want to allow only secure telnet session to connect and not allow
unsecure telnet on port 23. I looked on the telnet config and can see
where you can allow secure telnet but I don't see any place to not
allow unsecure telnet.

The same parameter that allows secure telnet can be used to block
non-SSL telnet. Do this:

CHGTELNA ALWSSL(*ONLY)

*ONLY means only allow SSL (and disallow non-SSL)

You can also configure it through iNav. Here's IBM's instructions:
http://tinyurl.com/enablessl

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.