finally finish implementing SOCKS5 proxies in ecore-con.
authordiscomfitor <discomfitor@7cbeb6ba-43b4-40fd-8cce-4c39aea84d33>
Wed, 15 Feb 2012 05:53:50 +0000 (05:53 +0000)
committerdiscomfitor <discomfitor@7cbeb6ba-43b4-40fd-8cce-4c39aea84d33>
Wed, 15 Feb 2012 05:53:50 +0000 (05:53 +0000)
commitf38e403907f5c5407a0ef571697a244511aaf293
treef29bd36f5fc52c956861cfa0e89293fc5019a931
parent8c0a9b06709874d4f3c3f7aaac511e6a6f8b1c94
finally finish implementing SOCKS5 proxies in ecore-con.
SOCKS5 is different from SOCKS4 in that it supports password authentication mechanisms (GSSAPI is still on the todo) and IPV6, neither of which are possible with SOCKS4

NOTE THAT THE CMDLINE SYNTAX FOR AUTOSOCKSING HAS CHANGED!
 *   ECORE_CON_SOCKS_V4=[user@]server-port:lookup
 *   ECORE_CON_SOCKS_V5=[user@]server-port:lookup

also note that I did not implement autosocksing with password. it's just not safe.

git-svn-id: svn+ssh://svn.enlightenment.org/var/svn/e/trunk/ecore@67959 7cbeb6ba-43b4-40fd-8cce-4c39aea84d33
src/lib/ecore_con/Ecore_Con.h
src/lib/ecore_con/ecore_con.c
src/lib/ecore_con/ecore_con_private.h
src/lib/ecore_con/ecore_con_socks.c