Original is at
http://www.socks.nec.com/socksfaq.html

SOCKS-client for WinSocket



Question List (Last updated May 16, 1997):




  1. What is SOCKS?
  2. How is socksv5 different from SOCKS V4?
  3. Is socksv5 interoperable with SOCKS V4?
  4. Where can I get SOCKS?
  5. Are there any SOCKS related mailing lists?
  6. Can I use SOCKS with Windows?
  7. Can I use SOCKS with a Mac?
  8. What do I have to do to modify programs to use SOCKS?
  9. Does SOCKS handle UDP?
  10. How does SOCKS interact with DNS?
  11. What is a single-homed and multi-homed firewall?
  12. Is there an RFC for SOCKS?
  13. What does SOCKS stand for?
  14. Why does the password echo when I run rftp?
  15. How do you traverse multiple firewalls (socksified SOCKS server?)
  16. Why do I see "inetd[]: socks/tcp server failing (looping)" in my logs?
  17. Can I use SOCKS with a OS/2?
  18. What causes the log message "incompatible version number: 71"?






http://www.socks.nec.com/ for more information.



Introduction to SOCKS for additional information.





ftp://ftp.nec.com:/pub/socks/. socksv5 is available through http at http://www.socks.nec.com/.


Both packages include clients for telnet, ftp, finger, and whois. NEC's SOCKS5 implementation includes archie, ping, and traceroute.


Several other clients are available in the same ftp.nec.com directory and at http://www.socks.nec.com/.


Hewlett Packard provides an internal implementation of SOCKS, available at ftp://ftp.cup.hp.com/dist/socks/socks.tar.gz


Many commercial products also include built-in SOCKS protocol support.



http://www.socks.nec.com/



http://www.socks.nec.com/.


A number of WinSock DLL extensions enable WinSock-based applications to use SOCKS:



There are also socksified WinSock Stacks, such as Peter Tattam's Trumpet WinSock at http://www.trumpet.com.au/wsk/winsock.htm.


Many commercial WinSock applications support SOCKS protocol.




http://www.socks.nec.com/how2socksify.html
for specific socksification details. You need to recompile the sources with pre-processor directives to intercept some calls such as bind(). The socks5 library can socksify TCP and UDP applications and the SOCKS V4 library can socksify TCP-based programs.


NEC's socks5 package includes some UNIX socks5 client shared libraries that can dynamically socksify programs without modifying or recompiling them. Refer to
http://www.socks.nec.com/.

See also Question 6.



SOCKS V4 protocol
and extension to SOCKS V4 protocol.


There are three RFCs for socksv5 related protocols:


  • RFC1928 - Describes SOCKS Version 5 protocol, also known as Authenticated Firewall Traversal (AFT).

  • RFC1929 - Describes Username/Password authentication
    for socksv5.

  • RFC1961 - Describes GSS-API authentication for socksv5





README file in the release.


NEC's socksv5 package includes support to traverse multiple SOCKS servers. Refer to http://www.socks.nec.com/ for additional details.




 Home

 What is new

 What is SOCKS

 SOCKS5

 SOCKS information

 NWSL



 Copyright

 SOCKS new vision

 Introduction to SOCKS

 SocksCap

 Visitor book







Send your comments and questions to
webmaster@socks.nec.com


Copyright © 1996, NEC USA, Inc.

All Right Reserved.