Looking for a little 'cheating' help.....

[erskie]

Not quite the place for this question, but it seems to be a tolerant forum... :)

At work I need to login every time I access the Internet. However, I noticed that when I logged into my happy home abyss server on any port other than 80, I did not need to login before it would let me past the firewall.

Soooo, I was wondering if there is such a thing as a simple redirect programme, such that I could access my home server from work on any port other than 80, and it could then re-drect my requests to 80, allowing me to surf the net without big brother knowing what I was doing? Or is it possible to set up a home webpage on an abyss server running on any port other than 80, and have some clever page do the port 80 requests?

Any ideas? I am a self-taught, self-confessed simpleton, so a simple explanation would be fantastic!

Cheers.

Oh, and thanks to everyone on this forum who has - unknowingly - helped me to set up my first secure site with forum. Simple for you all, a major achievement for me...

erskie

[iNaNimAtE]

Depending on how your work network is set up, this may or may not work:

Make a page on Abyss, and put this script in it.

Like I said, this may or may not work--so I promise no guarantee.
_________________
Bienvenidos!

[erskie]

Thks for the response. Will try.

[erskie]

The code works, but updates the main address in the window, so it does not solve my problem. However, when I placed the code in a frame the effect was much better ... will try it tomorrow at work!

[erskie]

Does not seem to work. Although the address in the bar stays constant, it still seems to use the local port 80...... any ideas?

[Anonymoose]

All that script does is load the other site in a frame - it doesn't proxy it through your home server or obfusicate the URL. The addresses which are seen by your work proxy will be exactly the same as before and so still blocked.

You need something a bit more complex. You could use CGI-Proxy but afaik that doesn't mangle the URLs so if your company has url filtering as well as site filtering, it still won't work perfectly.

[erskie]

Yes, they do have URL filtering too, in the form of a piece of software nastiness known as 'Websense'. However, am very interested in the CGI solution you recommend - could you give me some pointers? Assume total ignorance - and that is not much of an assumption :)

[TRUSTAbyss]

If all your looking for is a proxy , try
http://www.the-cloak.com , its free !

[Anonymoose]

TRUSTpunk most content filtering solutions will already have a known list of web proxies in their filter list, and also filter anything that looks like being a web proxy. I'd bet that the-cloak is already blocked - and if it isn't, it's going to look pretty suspicious in the log files when they're reviewed.

erskie, I literally meant a program called 'CGI-Proxy'

http://www.jmarshall.com/tools/cgiproxy/

Basically after setting it up, your machine at work will never make a request to any blocked site - your machine at home will be making the requests and then passing the result on to you. See the demo on the site above. However, as I said, that version doesn't mangle the urls by default - so for example when you visit slashdot, you'll see yoursite.com/blahblahbla/http/slashdot.org which will probably still get caught up in your filter.

You can turn on url encoding, but you will need a little bit of understanding of Perl to fix it...

[erskie]

I have just moved into my first house, which accounts for the delay in responding here ... apologies to those of you kind enough to continue taking an interest. I have to admit that it is nice to finally be able to drill holes, run cabling, etc. to be able to set up the network where I want it, instead of being restricted by apartment rentals....

I will take a look at the proposed solutions, but I would of course be interested in the URL mangler. Please let me know if the understanding of PERL required to do this is too much to address over this forum. I, sadly, know absolutely nothing about PERL.

Thks....

[iNaNimAtE]

[Anonymoose]

The URL obfusication in CGI Proxy is just a matter of uncommenting a couple of lines on closer examination.

iNaNimAtE, was it you who found some small change had to be made to CGI Proxy to get it to run on Abyss ?

[Axis]

Hi all--

Since I am running cgi-proxy on my abyss site I thought I would jump in. There is one configuration option that should be set. The "$NOT_RUNNING_AS_NPH= 1 ;" flag should be set. The proxy actually runs on abyss without this flag being set, however IE (at least 6) will not work unless the option above is chosen (though opera and mozilla will...funny, eh?)

Regards,
Axis

[Anonymoose]

Ah! Did you post about this before? I could remember someone mentioning it...

[Axis]

Hi Anonymoose--

Yes, in fact I did, though it was someone else here (on the forums) who helped me out..

Regards,
Axis