Socks proxy?
I'm not subscribed to the list, please CC: your replies to my mail address. I've been using Wget with an http proxy that doesn't support resuming (Proxy+), so I wanted to configure it for working with SOCKS but it doesn't seem to have that feature. I have a .wgetrc file on my HOME that says: http_proxy = http://10.0.0.3:1080/ ftp_proxy = http://10.0.0.3:1080/ (Socks proxy is waiting in the 1080 port). While it used to work when it was pointing to the HTTP proxy: http_proxy = http://10.0.0.3:4480/ ftp_proxy = http://10.0.0.3:4480/ Now it points to the socks one it fails at recognizing the headers when connected to the proxy. I also tried downloading the WgetPro sources and compiling those with --with-socks, but that didn't work that way either. As a matter of fact, if I do cd src; grep -i socks * I only get: config.h:/* Define if you wish to compile with socks support. */ config.h:#define HAVE_SOCKS 1 config.h.in:/* Define if you wish to compile with socks support. */ config.h.in:#undef HAVE_SOCKS Coincidencia en el fichero binario ftp-opie.o Coincidencia en el fichero binario wpro Which for me is crazy since it doesn't seem to use the HAVE_SOCKS variable at all, then I wonder how it could have socks support that way. I'm sure I'm doing something wrong, could anyone please tell me what? Thanks in advance. Best regards, -- H. Hernán Moraldo Moraldo Games http://games.moraldo.com.ar/
Re: Socks proxy?
The SOCKS support was added to Wget at a very early date and was unmaintained for a long time, up to the point where it wouldn't build at all. Since I didn't have the SOCKS library installed and noone even reported the failures, I decided to remove the `--with-socks' option from configure until someone stepped up to add back the support. In the meantime, the SOCKS library itself changed and porting new applications to use it became much simpler than it used to be. If you have the time, visit http://www.socks.permeo.com/TechnicalResources/SOCKSFAQ/SOCKSGeneralFAQ/HowtoSocksifyClients.asp and see if the listed steps work with Wget. As far as I can tell, Wget is SOCKS-friendly, according to guidelines at http://www.socks.permeo.com/TechnicalResources/DevelopDocuments/SOCKSFReferenceImpl120C.asp
Wget and Socks Proxy Support
Hello, There is information about Socks Proxy support on official website: > Supports HTTP and SOCKS proxies But in reality there is no support and there is no much instructions how to get it worked. Can we have some more information about this? How can we enable this library on Linux/Windows? May be this feature must be more developed or removed? P.S. Thanks to all programmers for their hard work on this product, I really like it. And special thanks to Christopher Lewis for his build (if its possible please make "sockified" builds too! :) ) Best reagrds, Bolee Menee
Re: Wget and Socks Proxy Support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bolee Menee wrote: > Hello, > > There is information about Socks Proxy support on official website: > >> Supports HTTP and SOCKS proxies > > But in reality there is no support and there is no much instructions how > to get it worked. Hm, yeah. I copied the features lists on the main GNU site and on the Wgiki, from a list that IIRC was present on the dotsrc.org website. But this particular feature-claim is very misleading, isn't it? My understanding, after a brief attempt to research this claim just now, is that the SOCKS-ified Wget is someone else's (mild) adaptation from the original Wget page. The distribution tarball for Wget 1.10.2 included some HTML files describing where to get a "socksified wget" (but the link currently resolves to an unmodified wget-1.10.2 tarball), and how to set up a somewhat involved and not generally-useful scenario where someone uses an HTML form to request that a CGI script (not included) download a file via Wget at a certain time. I've removed these files (which used to reside in util/) from the Wget 1.11 tarball, as they seem to be outdated, incomplete, and (for the link to a "socksified" Wget) incorrect. After downloading the source code for socks-server and reading a file called How-to-SOCKSify, it appears that socksification consists of adding an initialization-function call to the top of main(), Passing -D flags to gcc to #define connect=Rconnect, etc, and linking with libsocks. If that's what the socksified Wget is/was, then it would appear that the socksified Wget can _only_ communicate with a SOCKS server, and can't make normal connections anymore. Hrvoje, Mauro, is this accurate? - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHp+R07M8hyUobTrERAsztAJ4+9XJ2YeT74zuwpRmAdJT7y+8hjACfdneK 9wJ3rrhz3pafCXinDvT71+w= =MAa/ -END PGP SIGNATURE-
Re: Wget and Socks Proxy Support
> Bolee Menee wrote: > > Hello, > > > > There is information about Socks Proxy support on official website: > > > >> Supports HTTP and SOCKS proxies > > > > But in reality there is no support and there is no much instructions how > > to get it worked. > > Hm, yeah. I copied the features lists on the main GNU site and on the > Wgiki, from a list that IIRC was present on the dotsrc.org website. > > But this particular feature-claim is very misleading, isn't it? > > My understanding, after a brief attempt to research this claim just now, > is that the SOCKS-ified Wget is someone else's (mild) adaptation from > the original Wget page. The distribution tarball for Wget 1.10.2 > included some HTML files describing where to get a "socksified wget" > (but the link currently resolves to an unmodified wget-1.10.2 tarball), > and how to set up a somewhat involved and not generally-useful scenario > where someone uses an HTML form to request that a CGI script (not > included) download a file via Wget at a certain time. I've removed these > files (which used to reside in util/) from the Wget 1.11 tarball, as > they seem to be outdated, incomplete, and (for the link to a > "socksified" Wget) incorrect. I've not checked a more recent release but wget-1.10.2 has references to both a; '--with-sox' and a '--with-socks' configure option but neither do anything AFAICT. > After downloading the source code for socks-server and reading a file I think only the socks client S/W is needed to built a sockified wget. > called How-to-SOCKSify, it appears that socksification consists of > adding an initialization-function call to the top of main(), Passing -D > flags to gcc to #define connect=Rconnect, etc, and linking with > libsocks. If that's what the socksified Wget is/was, then it would > appear that the socksified Wget can _only_ communicate with a SOCKS > server, and can't make normal connections anymore. > > Hrvoje, Mauro, is this accurate? This sounds like the old Socks 4 sockification procedure. For socks 5, somthing like the following should work, where $PWD/../socks5-1.0r11-3/socks5-v1.0r11/installdir is the root of a (temporary) installation of the socks client library S/W. ./configure CFLAGS="-O2 -Wall -Wno-implicit -DSOCKS \ -I$PWD/../socks5-1.0r11-3/socks5-v1.0r11/installdir/include"\ LDFLAGS="-L$PWD/../socks5-1.0r11-3/socks5-v1.0r11/installdir/lib" \ LIBS="-lsocks5" make I tried this a while back with wget-1-10.2 but it just dies with segfault. Regards Tom. -- Tom Crane, Dept. Physics, Royal Holloway, University of London, Egham Hill, Egham, Surrey, TW20 0EX, England. Email: T.Crane at rhul dot ac dot uk Fax:+44 (0) 1784 472794
Re: Wget and Socks Proxy Support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: | I've not checked a more recent release but wget-1.10.2 has references to | both a; '--with-sox' and a '--with-socks' configure option but neither do | anything AFAICT. You mean in utils/README, right? Yeah, but that's talking about the special "socksified wget", not the official wget-1.10.2 sources, I think (though it doesn't at all make that clear). |> After downloading the source code for socks-server and reading a file | | I think only the socks client S/W is needed to built a sockified wget. Right. The socks client, as I understand it, is available with the whole socks-server package. |> called How-to-SOCKSify, it appears that socksification consists of |> adding an initialization-function call to the top of main(), Passing -D |> flags to gcc to #define connect=Rconnect, etc, and linking with |> libsocks. If that's what the socksified Wget is/was, then it would |> appear that the socksified Wget can _only_ communicate with a SOCKS |> server, and can't make normal connections anymore. |> |> Hrvoje, Mauro, is this accurate? | | This sounds like the old Socks 4 sockification procedure. Yeah, it is. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHqgSm7M8hyUobTrERAghRAKCC9blByPJi6TpxBvRWYymCR+uNbACeJIGq Uf8pMntGPkXQYSafthTdW9A= =XN25 -END PGP SIGNATURE-
Re: Wget and Socks Proxy Support
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After some more digging, it looks like I was wrong about the "socksified" Wget being something different from the official sources; according to the news file, socks support was introduced in Wget 1.4.0. I don't have access to 1.4 sources, but Wget 1.5.3's configure script has the --with-socks option. The configure option was removed during the development of 1.9; according to comments it was because the check was broken. Looks like a feature that's gone the way all unmaintained code must. :) I'll remove the references from the manual and web pages. I'd like to put SOCKS support back in at some point, though my plans are to make it a configurable part of Wget, like the HTTP proxy support. However, it'll be a while before that support's in, so if in the meantime someone wants to bring the old functionality back up to snuff, I'm happy to accept patches. :) - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHqp1A7M8hyUobTrERAkl/AJ9+g6ZHqygdkiV36f+q6w3tLgcEmgCfVCwG azdZ8xozoFhIYAYDH+MBSJY= =Q4wC -END PGP SIGNATURE-
