Yup, and that means I have a pretty restrictive firewall.
Oops! Google Chrome could not connect to ec2-50-18-7-165.us-west-1.compute.amazonaws.com:8081 <----
Yup, and that means I have a pretty restrictive firewall.
Oops! Google Chrome could not connect to ec2-50-18-7-165.us-west-1.compute.amazonaws.com:8081 <----
http://wiki.freaks-unidos.net/weblogs/azul/firefox-ssh-tunne...
This is a decent example. I've seen others that have more options and presumably more functionality.
A few notes from past experiences. Your IT department will completely freak out. Hopefully they'll also be impressed. HR will freak out worse because they won't understand. A good IT employee will come see what the heck is up with your ssh throughput to a weird vps or home box - befriend this person if you haven't already. Average code-monkeys will be impressed, especially if you don't do web development. Finally, it's almost certainly a violation of that 20 page agreement you signed on the first day of work.
I have such a setup for accessing Pandora at work. We are in the UK, so we have to trick Pandora into thinking I'm from the US. Nobody at work cares.
Screenshot, pretty please?
Speaking of which, what is the legality of your corporation injecting fake SSL certificates for sites served over HTTPS?