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.
This is what I do to get around blocks on some IM services. I work for a large, well-known and presumably IT-savvy organization. Nobody has confronted me about it yet, which in itself is actually kind of worrying. I half expected an IT SWAT team to rappel through the window after starting the tunnel.
Where I work, we have to ssh tunnel. Our cvs, bug tracker, internal websites and other servers are all located on the other side of the world, and only accessible through a tunnel.
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.