![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
This is fantastic programming on BBC4, random journalist whose name I have no idea of, wandering about various "Stanese" countries with a camera.
Anyhow, geeky! I've set up mainpc running an SSH server on port 443 which is should then forward to a proxy on localhost, running on port 8080 (which has always been running there for traditional reasons), which should then allow me to browse the web with no restrictions, and will hopefully also allow me to SSH out from work! Maybe. Possibly :)
As I don't have windows running here right now, I'll have to check it works tomorrow (if I decide to do some o/t in the morning) or Wednesday. Hmm.
I have more pork cooked and cooling in the fridge. Uhhm.
Why do I bother writing here when life is this boring? :)
Anyhow, geeky! I've set up mainpc running an SSH server on port 443 which is should then forward to a proxy on localhost, running on port 8080 (which has always been running there for traditional reasons), which should then allow me to browse the web with no restrictions, and will hopefully also allow me to SSH out from work! Maybe. Possibly :)
As I don't have windows running here right now, I'll have to check it works tomorrow (if I decide to do some o/t in the morning) or Wednesday. Hmm.
I have more pork cooked and cooling in the fridge. Uhhm.
Why do I bother writing here when life is this boring? :)
(no subject)
(no subject)
Think it'll work?
Depends how your work's firewall is configured. If they have any sense, they'll have closed all ports by default, and white-listed those that are needed, e.g. 80, 21, etc. Even then, chances are that the white-listed protocols are logged, with your desktop's IP against each request and session.
At best, they'll see that you're tunneling megabytes of data through a logged protocol.
Oh, they're a communications company, so I really do expect they know that they're doing with IP.
Re: Think it'll work?
It is proxied, however. I do believe that PuTTY can deal with proxied SSH connections, though I ain't 100% sure. So this could be the biggest downfall.
At worst, there'll be a meg or two's worth of data going through my connection in a day (it'll only ever be used for SSH back to my home PC, they only block websites like hotmail and other "naughty" sites), so that won't be any more than usual. And it's hardly unusual to see a fair bit of port 443 traffic.
And just because the company deals primarily in comms, doesn't mean the IT dept know anything about it. It's all outsourced (to a company called Pink Roccade if you know anything about them). They do seem to know a fair whack though, and everything is pretty closely locked down.
I'm yet to find a way to break anything, but I did have lots of fun with "net send" when I first managed to get a command prompt open *G*
Re: Think it'll work?
Anyway, good luck with your tunnelling! Let me know how you get on.
Re: Think it'll work?
TBH I don't think there are many people in the actual Cust Serv world who could tell you a single thing about how IP works, what a packet is made of, what MTU means and so on.
The business is reliant on very specialist departments. Network and Cust Serv have no lines of communication. In fact, I often feel that cust serv have no lines of communications with anyone ;)
Re: Think it'll work?