A decent number of things are blocked where I work. SSH is not. I usually use git via SSH. I did want to clone someone's repo that was shared over the git protocol, so I typed in the git-clone command, and waited. It timed out. The quick fix would be to clone it to my home machine, and then clone it over ssh. I never like doing that though, I like origin being the actual origin. I decided that it shouldn't be too hard to get a clone to work, so I did a bit of googling. I figured that if git had any support for a proxy server, it'd be possible one way or another.

I figured that I could use a combination of the "netcat" utility and ssh to get the desired result. I found the following article: http://twopenguins.org/tips/git-through-proxy.php that ...

I don't believe in blocking anything on the Internet. It only creates problems. Anyone with a technical know-how can easily get past any filtration system. Most would be surprised how easy some filters are to bypass. I'm not writing this blog post to condone nor endorse filtering, nor getting around a filter that is in place wherever you have access to the Internet. I am only interested in making the necessary knowledge available to those inclined to seek it out.

When getting around an Internet filter, you need to know the type of filter that is in place. Some firewalls block all traffic to a specified computer or network on the Internet. Some only block web traffic. Some block only IRC traffic. Know what you are trying to get access to, and know how it is being blocked.

The block that prompted this blog post is BYU's ...