Blocked again.

[johnridley]

The damn blocking software here at work is blocking LJ again. The net effect is that none of the javascript stuff (previewing, flist filter selection, etc) works, since I have to go through a PHP proxy. Just irritating. It was unblocked for several weeks and I had just about forgotten what a PITA it is when it's blocked.

Comments

[c0nsumer.livejournal.com]

PuTTY + remote server + Firefox with net.proxy.socks.remotedns (or so) set to TRUE.

Need a fast local shell?

[johnridley.livejournal.com]

I have only one port (443) that's clear out of my workplace and into my house. I'm using that for my Myth box so I can access/change programming and some other stuff from away from home.

If I could find another port to use, I'd be running a proxy for sure. But outside of that the PHP proxy works pretty well, other than things are a bit gummed up.

I did play with using Apache in proxy mode a while back but I didn't like it.

[c0nsumer.livejournal.com]

Can you take PuTTY, tell it to use an HTTP proxy (put yours in there), but still connect to whatever:22? If you can, you can do it...

[johnridley.livejournal.com]

Sure, I can do that, for one day, then I'd get my pink slip the next day. I do use SSH to business servers, but if port 22 traffic crosses the firewall, they'll ask you why.

Even then I'd have to use my coloc'd server, only port 443 is clear on both outbound at work and inbound on my cable modem.

Believe me, we've been through all the workarounds, and a PHP proxy is the only one that both works and won't get us fired (and even the latter is just because they haven't specifically banned it - if it were widely known that it was going on, they would and that would be gone).

[c0nsumer.livejournal.com]

Oh, ergh. Yeah, that wouldn't work. :\

[kevinnickerson.livejournal.com]

It's so much easier when you're the person in charge of stuff.