Secure TELNET -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

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

Subject: Secure TELNET
From: "John.BresinaJr" <John.BresinaJr@xxxxxxxxxx>
Date: Mon, 10 May 2010 14:57:23 -0500
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>

What options are people using to Secure Telnet?

Our auditors are requiring TELNET to be secured/encrypted for all users by the end of the year. 1st they wanted us to user IPSec(VPN tunnels). This turned out to be a nightmare because IBM doesn't allow wildcards in the DN entry so you would have to create a tunnel for each and every connection to your system. Then they wanted us to us SSH. But it appears that you once again would have to setup a tunnel that the real Telnet traffic could then flow through. I am sure that business team members don't want to end up at QSH.

John Bresina Jr| Engineer | TTS Server Tech iSeries | *Target | 33 S. 6th St.| Minneapolis, MN 55402 | 612 304 3665 (ph) |

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Secure TELNET , Lukas Beeler

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.