Proxies

[Sawell]

As it stands, at work... I can do piss all other than surf the web.

I can't use msn, irc, mir, nowt.

Some of this I can circumvent using a HTTP proxy, but those holes get closed up quicker than a straight guy who accidentally walked into a gay bar.

Currently I use a proxy to be able to connect to the web at work (using port 8080), I obviously can't port forward because I'm not an admin, SSH is blocked so I can't set one of those up at home, I can't just use a proxy because there is already one in place... so what do I do?

I thought I might be able to setup some kind of proxy chain? Linking the one I'm already in to another one, which will allow me to do what I want.

 

[Sawell]

Actually, does anyone have an SSH server I could try? On a non-obvious port (don't do 22!)

 

[LeoCrasher]

Why can't you use SSH?

I use SSH in a very restrictive environment, I don't see why you can't .

1. You setup the SSH server at home using OpenSSH. Stick it on one of the common ports like 21, 80, etc.
2. Download Portable Firefox and PuTTy on a USB stick.
3. At work, configure PuTTy to connect to your OpenSSH box at home, using the work proxy as the intermediatary (there are options for configuring the proxy).
4. In putty, you will need to tunnel ports such as 8080 to your OpenSSH box. It will proably just require you entering 127.0.0.1 on 8080 as a dynamic port.
5. In firefox, configure it to use the proxy server 127.0.0.1

Done ^^
/Leo

 

[Sawell]

Why can't you use SSH?

I use SSH in a very restrictive environment, I don't see why you can't .

1. You setup the SSH server at home using OpenSSH. Stick it on one of the common ports like 21, 80, etc.
2. Download Portable Firefox and PuTTy on a USB stick.
3. At work, configure PuTTy to connect to your OpenSSH box at home, using the work proxy as the intermediatary (there are options for configuring the proxy).
4. In putty, you will need to tunnel ports such as 8080 to your OpenSSH box. It will proably just require you entering 127.0.0.1 on 8080 as a dynamic port.
5. In firefox, configure it to use the proxy server 127.0.0.1

Done ^^
/Leo

Yeahyeah I got putty, tried all this before lol... common SSH ports are closed.

Doing a full local port scan as we type.

Warning! TCP port 135 open
Warning! TCP port 445 open

Woop. Done 600 so far.

 

[Sawell]

Oh, the problem I have with my home server is that my internet is gay, well, it's windy and it screws up.

I can set it up on my dedicated server though, then share it with the world.

 

[LeoCrasher]

Obviously the proxy isn't going to allow you to connect to other non-HTTP ports. So stick it on a common port!

Doing a port scan of what ports are open on the p.server will not tell you what ports it will allow you access to outside its local network. It will merely tell you what ports it ha available. Afterall you are going to have to connect to its port 8080 no matter what you do, as its the only way out of the network.

Port 443 is the HTTPS port, and Port 80 is the HTTP port. Your OpenSSH server will work on either of them, and the work proxy will have no issue in allowing you access to them.

/Leo

 

[Sawell]

Obviously the proxy isn't going to allow you to connect to other non-HTTP ports. So stick it on a common port!

Doing a port scan of what ports are open on the p.server will not tell you what ports it will allow you access to outside its local network. It will merely tell you what ports it ha available. Afterall you are going to have to connect to its port 8080 no matter what you do, as its the only way out of the network.

Port 443 is the HTTPS port, and Port 80 is the HTTP port. Your OpenSSH server will work on either of them, and the work proxy will have no issue in allowing you access to them.

/Leo

You've lost me :| didn't you suggest the FTP port earlier!?! That's a non-http port X_X.

 

[LeoCrasher]

¬¬ yes, but can you access other FTP sites using the proxy? If so then 21 is fine. If not, 443 is the better choice.

/Leo

 

[Sawell]

¬¬ yes, but can you access other FTP sites using the proxy? If so then 21 is fine. If not, 443 is the better choice.

/Leo

But 443 is closed by admiN!!!!!!!!!one.

Isn't that the function of a port scanner?

 

[LeoCrasher]

Your telling me that you seriously can't access https://www.google.com/adsense/ (notice the HTTPS - means its on Port 443)

If you can access that site. Port 443 outbound is not closed.

/Leo

 

[Sawell]

Oh ffs I'm such a dumbass.

Inbound/outbound... yeah I'm clever!

Thanks for putting up with my blonde moment Leo. ^^

 

[LeoCrasher]

:P so put the OpenSSH server on Port 443 , make sure you've made the groups/passwords config file... then connect with putty.

Oh, and don't forget to input your work proxies settings into putty, otherwise it will attempt the network gateway and get nowhere.

/Leo

 

[Sawell]

:P so put the OpenSSH server on Port 443 , make sure you've made the groups/passwords config file... then connect with putty.

Oh, and don't forget to input your work proxies settings into putty, otherwise it will attempt the network gateway and get nowhere.

/Leo

If only I could use RDC here.

What's that? You don't mind connecting and setting it up for me? :O

 

[LeoCrasher]

Np. Send details and I'll set the whole thing up.

/Leo