Re: Allowing only secure telnet -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Allowing only secure telnet
From: Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>
Date: Mon, 10 Nov 2008 12:17:45 -0600
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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.

Follow-Ups:

RE: Allowing only secure telnet , Mike Cunningham

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