41g.net
The place to be
sock proxy server
sock proxy server
SOCKS is an Internet protocol that allows client-server applications to transparently use the services of a network firewall. SOCKS is an abbreviation for "SOCKetS" .
Clients behind a firewall, needing to access exterior servers, may connect to a SOCKS proxy server instead. Such proxy server controls the eligibility of the client to access the external server and passes the request on to the server. SOCKS can also be used in the opposite way, allowing the clients outside the firewall ("exterior clients") to connect to servers inside the firewall (internal servers).
The protocol was originally developed by David Koblas, a system administrator of MIPS Computer Systems. After MIPS was taken over by Silicon Graphics in 1992, Koblas presented a paper on SOCKS at that year's Usenix Security Symposium and SOCKS became publicly available. The protocol was extended to version 4 by Ying-Da Lee of NEC.
Unofficial SOCKS 4a extensions add support for DNS names to resolve names with SOCKS server. The current version 5 of the protocol, RFC 1928 or authenticated firewall traversal, extends the previous version by supporting UDP, authentication, letting the SOCKS server resolve hostnames for the SOCKS client, and IPv6.
The SOCKS reference architecture and client are owned by Permeo Technologies, (note that Permeo Technologies has been bought out by Blue Coat Systems ) by a spin-off from NEC.
According to the OSI model it is an intermediate layer between the application layer and the transport layer.
Even more about sock proxy server
Pakistan Hackers Club ::: eLibrary :: Bypassing Firewall or Proxy ...
This SOCKS client when receive a particular request for the user system, it tunnel the request through http port to the main SOCK proxy server. Since, http port is usually allowed through the firewall ...
Error in the Java Standard Library while using Tor sock proxy
Error in the Java Standard Library while using Tor sock proxy; From : Myers Carpenter < myers@maski.org > ... Reply from SOCKS server contains wrong code at java.net.SocksSocketImpl.connect(SocksSocketImpl ...
