Hello Gino and Dido,
Thanks, those are pretty clever solutions.:) The biggest obstacle I could see actually, is getting the organization that owns the remote server to enable telnetd listening to only the loopback address (sadly, this is more of a political issue).
I forgot to mention that the legacy app doesn't run on linux (unlike the remote server counterpart) ..but runs DOS (!). I'm looking for an SSH client for DOS right now that supports tunneling and I'll see what I can do.
This is an interesting situation for me, only now was I aware of the scope of legacy apps running in organizations that are perform critical functions, and yet rely on deprecated protocols. I guess that sometimes we simply can't expect them to fully migrate right away, but be creative and make a good compromise between backward-compatibility and current-technology.
Thanks and more power!
======================================= Paul Patrick Carpio Prantilla Assistant Professor
University of the Philippines Los Banos Institute of Computer Science =======================================
-- Philippine Linux Users' Group (PLUG) Mailing List plug@lists.q-linux.com (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
