Derrick 'Red 5' Cole wrote:
| 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.
There are a couple of shims that sit above winsock now, rather
than mucking with it. V-One makes one, theres another called VTCP.
You point your network program to 127.0.0.1 on some port, and it wraps
the connection in an 'secure pipe' to the firewall. V-One offers the
nice ability to control where users connect to once they connect over
On the down side, you find yourself saying 'the V-One client
server protocol' or 'the V-One online registration protocol' an awful
lot, and they're both mouthfuls.
Pet peeve of the day: Security companies whose protocols dare not
speak their name, because they don't have one. Guilty company of the
day is now V-One.