This is an interest check for SSH tunneling proxy service to bypass school or parental filters stopping you reaching this forum. Or whatever. Previously I tried to get one of the shell account providers I staff (one focusing on censorship evasion) to take people like you guys as users, but they want Syrians and Chinese, not students who can't browse web forums.
I have the space to set up my own. If you might be interested in this, check below how it will work and what would be required, and indicate in the poll whether it would be useful for you.
You would need to be able to download PuTTY or a similar SSH client that has an option for a Dynamic Tunnel ("-D"). This can be gotten as a standalone executable, so there's no need to have privileges to install programs. If you're running Mac OS or Linux, you will already have a command-line SSH client (easy, set and forget).
The SSH server will listen on ports 22 (SSH) and 443 (usually HTTPS). This will allow access through some firewalls that restrict traffic to HTTP and HTTPS. Some firewalls will be able to tell that it isn't actually HTTPS traffic so this may fail in some cases.
For example, you might SSH to the server and specify in the options a dynamic tunnel on port 9090.
Once the SSH connection is established, you would tell your browser to use a SOCKS proxy at localhost:9090. After that, the browser traffic should proxy via the SSH server. The connection between your PC and the SSH server would be encrypted, helping to bypass some policies.
Once the data arrives at the SSH server, that will be decrypted. Will this open the users to privacy concerns? Maybe. The data could also be encrypted for an SSL connection between your PC and the remote web server (e.g., SS, once Soul sets up SSL). If the data is in plaintext (aside from the SSH encapsulation) it is possible to eavesdrop, but I have things to do and I can assure you I don't care about whatever it is. But if you already use proxies you're familiar with the idea that you have to trust a sysop at some point.
If you want to test
whether this would work for you, get putty.exe
and tell it to connect on SSH to anapnea.net on port 443 (all of that is configured in the first window you see, before you hit Connect). If you get a prompt for a username, then you can use this solution. You might also try port 22 in case that traffic is allowed, but the firewall is dropping the port 443 traffic for not actually being HTTPS.