> Ken Hardy finally said...
> >"That would justify a proprietary implementation, perhaps, but would not be
> >incompatible with parallel support for Standard Socks TCP clients."
> Given that WinSock is specifically designed to implement BSD Sockets in
> a Microsoft Windows environment, anything that Microsoft does to
> implement the of remoting WinSock applications will be proprietary to
> the Microsoft Windows environment due to the nature of the API in
Hmm... on the Client side this is true. But we are talking about firewalls.
One can't use Microsofts Catapult as a firewall for Unix Systems running
Socks Clients, since the Firewall doesnt understand the Protokoll. With
Socks you can use a Unix-FW to proxy MS Clients and you can use Unix-Clients
Anyway.. what are the IP Firewalling capabilities of the Catapult System?
(OO) -- Bernd_Eckenfels @
( .. ) ecki @
o--o *plush* 2048/A2C51749 eckes @
irc +4972573817 *plush*
(O____O) If privacy is outlawed only Outlaws have privacy
From: Russ <Russ .