You might be thinking about the wsock32.dll put out by Hummingbird which is a 32-bit winsock replacement for Windows95 and Windows NT. Dunno if one exists for Win3.1. You can download the Hummingbird wsock32.dll for free from their homepage: http://www.hummingbird.com/
For DOS/Windows, I believe FTP and other stack manufacturers have come out with SOCKSified stacks.
From: Nick Keenan[SMTP:nkeenan @
Sent: Tuesday, June 25, 1996 1:13 PM
To: David j. Sopuch
Cc: firewalls @
Subject: Re: SOCKS protocol.
>My question is:
>How popular is SOCKS?
I posted the same question here a few months back, and was absolutely
underwhelmed by the response. (2 I think). I understand that these security
guys are VERY reluctant to discuss the details of their internal
implementations. That said, I went ahead and put SOCKS support into my
application. My intuition is that very few users are using it -- I get a
lot more calls asking how to set up mapped links than SOCKS. I suspect also
that a lot of places have SOCKS and nobody knows about it.
>Can we wait for winsock makers to support it, or must every
>application that wants to open sockets have support for
I read recently about a software "shim" that would go between the
application and winsock.dll, and "SOCKSify" all winsock requests. In
theory, this could be used with any winsock stack (although anyone who has
worked with more than one winsock package would be justified in doubting
that claim). The security experts on the list can offer their opinions as to
whether this would be acceptable from a security standpoint.