On Thu, 30 Jan 1997, Allen D. Harpham wrote:
>
> They use a windows based telnet package that they would like to use to
> access their hosts on the internal network over the internet.
This is the behaviour purported by this "shim" idea. It situates itself
in the midst of the winsock stack, and "knows" (most likely via routes to
destinations using pseudo interfaces - as with swIPe) when to encrypt a
session and when not to.
> BTW, the internal hosts are not running unix. They are running a
> propriatary operation system that supports telnet. So I assume the best
> thing would be to setup a telnet server behind the firewall and have them
> first telnet into the telnet server and then telnet to the internal host.
> Correct me if I am wrong.
The firewall could be your telnet server. Any reason to have an internal
one?
Derrick
--
/ Derrick Cole (derrick .
cole @
ssds .
com)
____/ ____/ ___ / ____/ Suite 1000, Two Hannover Square
____ / ____ / /__/ / ____ / Raleigh, NC 27601-1764
_______/ _______/ _______/ _______/ (919) 856-1441 Fax (919) 856-1455
business-driven technology solutions January 31st, 1997
Follow-Ups:
References:
|
|
