From: Michael F. <mi...@pc...> - 2004-12-29 10:46:33
|
Jose Bernardo Silva wrote: >That sounds very promising. I'll try and install it on my server, and test it >soon. I fear now I really have to learn Python, because without url >obfuscation I really can't risk much more than testing a few "inocuous" urls. > > Good news and good news. Python is *very* easy to learn. If you've done any programming before then you already know most of python basics. Second good news - I'll add URL obfuscation for you, if you help me test. (You ought to learn python anyway.. it really is a lovely language). approx works by rewriting URLs in the CGI - so that accessing links go through the proxy. Since it is rewriting URLs already... obfuscating them really is very easy. When you use the clientside proxy, the URLs are modified by the clientside and approx knows to leave them alone. I would just need to plug the same bit of code into the clientside and the server side. As I said, the clientside proxy needs work though. Regards, Fuzzyman http://www.voidspace.org.uk/python/index.shtml >On Wed, 29 Dec 2004 10:19:57 +0000, Michael Foord wrote > > >>I've written a CGI proxy in python called approx. >>http://www.voidspace.org.uk/atlantibots/pythonutils.html >> >>It needs to be installed on an external server with Python 2.2 +. >>This will be almost all Linux servers. >> >>It doesn't *yet* do URL obfuscation - but that would be *trivial* to >>add. When used just as a CGI it only modifies webpages - it doesn't >>work with Javascript. However - when used with a clientside proxy as >>well (browser connects to localhost - clientside proxy connects to >>approx). >> >>The clientside proxy is still 'alpha' - I've had it working (and >>used it regularly) via our company proxy - but it didn't work with a >>direct connection. Help in testing would be appreciated. Because it >>proxies all connections from the browser - things like javascript >>work fine. >> >>Note for Wayne - if you wanted to build in support for approx into >>localproxy, it would be *very* easy. The url's just need rewriting >>for the approx location. It's an http/ftp only proxy of course. >> >>Regards, >> >>Fuzzy >>http://www.voidspace.org.uk/python/index.shtml >> >>Jose Bernardo Silva wrote: >> >> >> >>>Hello! >>> >>>I am using now another software to bypass the corporate firewall censorship >>>measures. The use NTLM for authentication, websense for the censorship >>>software. My problem is that the sw that I use now, hasn't been updated in >>>over 2 years, and doesn't support "translating" much of the javascript being >>>used to navigate inside sites. >>>I was thinking of using proxytools instead, but I need to know if the url's >>>are obfuscated when they are sent thru the corporate proxy (as it is done by >>>the sw that I use now), or are they sent in plain view? If so, I can't use >>>proxytools, as accessing competitors websites or recruitment sites is reason >>>for disciplinary procedures, so finding a url for one of those in the ISA logs >>>would get me into trouble. >>>Thank you! >>> >>>PS: I have a server outside the corporate network with cgi access, so I can >>>always put a script or a program there to obfuscate the urls and proxy >>>everything... >>> >>> >>> >>> >>> >>------------------------------------------------------- >>SF email is sponsored by - The IT Product Guide >>Read honest & candid reviews on hundreds of IT Products from real users. >>Discover which products truly live up to the hype. Start reading >>now. http://productguide.itmanagersjournal.com/ >> >> >_______________________________________________ > > >>proxyTools-users mailing list >>pro...@li... >>https://lists.sourceforge.net/lists/listinfo/proxytools-users >> >> > > > > |