SSH Tunnel Was( Re: script to change Client Access .ws profiles)

Scott answered it pretty good, although I was not thinking of using another PC to be the endpoint of the SSH tunnel, but instead using the 400.
There is some very good info out on the net to make this happen. Since we are using this discussion in the system i arena here is a good example setup:
http://www-912.ibm.com/s_dir/slkbase.nsf/1ac66549a21402188625680b0002037e/16b6e5bb811e4a628625711b007b8bf6?OpenDocument&Highlight=2,ssh
-or-
http://tinyurl.com/2hrnkt

and from the main site:
http://www-03.ibm.com/servers/enable/site/porting/tools/openssh.html

<snip>
--You can use ssh to encrypt the 5250 telnet datastream:

* On the server, start the telnet server and the sshd server
* On the client, start an ssh session to the server (named servername in this example) that will route the traffic on an unused port on the client (2001 in this example) to the telnet port (23) on the server:
CALL QP2TERM
then
ssh -T -L2001:localhost:23 servername
This ssh session will need to be left active while the tenet sessions are in use
* Other sessions on the client can now start telnet sessions:
TELNET RMTSYS(*INTNETADR) INTNETADR(LOCALHOST) PORT(2001)

</snip>

Bryan



John Earl said the following on 8/15/2007 1:46 PM:

Bryan,

Good question, and I suppose that I should know this (but I don't -
that's why I hang out here :), what are some of the 5250 telnet clients
that support SSH?
jte