Re: OT: Geekness - avoiding proxies

On Mon, 06 Mar 2006 06:53:52 -0500, "doetnietcomputeren"
<doesnotcomputeDELETE@xxxxxxxxx> wrote:

I know this has been discussed briefly before, but I'm in need of some
rather more basic help.

At work, I'm stuck behind a websense proxy. This bars many things, some
reasonable, some otherwise, many I don't care for. However it also bars
web traffic to certain ports, 2082 and 8443 being two such examples.

I'm aware that if I have an always on machine (at home for example) that
is plugged into a broadband connection, I should be able to do something
geeky that enables me to connect from work, to the desired ports via the
machine at home.

Anyone able to give me some reasonably simplified help, including any
software recommendations? Oh and installing software on my work PC isn't
ideal - it's do-able, but I'd prefer not to.

Up until recently I was EKS at BT and didn't much like the idea of
their clueless IT permies knowing where and when I was surfing. The
approach I used was to run a squid proxy server on a linux box
connected via home DSL connection. The only thing you need to install
on your works PC is an ssh client (putty does the job, though I had
cygwin installed for other reasons). Then pick a local port (choose
something obscure like 10010) and tunnel that port via ssh to your own
proxy server.

Then all you need to do when you fancy some covert skiving is change
your browser proxy settings to localhost:10010 (or whatever your
chosen port is). I used to keep my firefox permanently set up to use
my own proxy server and use IE for intranet / work related stuff.

I think BT got wise to people hiding their activity in this way
because one day I arrived at the office and they had firewalled off
outbound port 22. Just set your sshd to listen on another port as well
as 22. Job done.

Obviously this approach is not limited to http traffic. You can tunnel
whatever you fancy to wherever you fancy.

--
SimonM
GSX-R 1000 K5

Spamtrap - change "deadspam.com" to "veryblack.co.uk"
.

Relevant Pages

  • Re: Transparent proxy failing
    ... machine A as the gateway on the network, and A takes requests to port ... The squid machine, A, doesn't handle HTTPS blocking. ... up a website, it goes right to the website, no filtering. ... IE on the client to specifically use the proxy setting of B's ip ...
    (Ubuntu)
  • Re: SSH Tunneling, view web site as though I am in the USA
    ... $ ssh -D 1080 me@us_server ... And then set your local web browser to proxy using socks 4 to server ... HTTP Proxy: localhost Port: 1080 ... Not http proxy, SOCKS 4 proxy. ...
    (comp.security.ssh)
  • Re: Fehlercode 502
    ... Wenn ich den Proxy umgehe, ... In der ISA Server Hilfe habe ich leider keine Infos gefunden, ... Gruß Detlef ... >> Port 8443). ...
    (microsoft.public.de.german.isaserver)
  • Re: Webproxy Konfiguration auf einem ISA 2006 Standard
    ... dann ist der Client noch SecureNAT Client?! ... Dann geht es auch ohne Proxy ... Hierbei habe ich die einzelne IP als Quelle angegeben und den ISA ... Freigegeben sind Port 80/443/8080. ...
    (microsoft.public.de.german.isaserver)
  • How are they broadcasting through my proxy server?
    ... where xxx.xxx.xxx.xx represents the external IP of the proxy server ... and is not allowing anything to pass through port 135... ... The popup message never actually appeared on the proxy server itself, ... I taught that once I turned on the packet filtering, ...
    (comp.security.firewalls)