Re: Remote Access (Again) -- MIDRANGE-L

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

Subject: Re: Remote Access (Again)
From: Edward Marczak <erm@xxxxxxxxxxxxxxxxxxxx>
Date: Wed, 04 Dec 2002 20:36:39 -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/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Whew!  Look what I started...sorry! (actually, security is a great topic to
keep refreshing one's self about).

Anyway, I certainly understand the risks that telnet and clear text leaves
open.  Being new to the AS/400, I wasn't sure if there were any other
methods of (direct) remote access.

Since the machine in question is running V3R2, I don't have SSL available to
me.  Looks like I need to set up a VPN, ssh tunnel, etc.

Thanks everyone, for all of the feedback!
--
Ed Marczak

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Remote Access (Again) , Adam Lang

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.