This is done by using an Access Control List on apache to allow access to the protected area ONLY from itself. With MITM attacks becoming more prevalent and government spying, I would prefer to use a tunnel to access to connection instead. Secure Admin Area Logins If I am a road warrior and need to access a secure area, I might trust a simple https connection. Unless it also has access to the server and the network it resides on, they will not know what happens from that point. My ISP would still show a SSH connection to the server, but that’s it. With a socks proxy and the option to tunnel web traffic including DNS requests through the tunnel, everything will appear to come from the server, not my client. Furthermore, my ISP could read my DNS queries normally, so an encrypted connection would still show that I went to. A socks proxy uses the server I SSH into instead of my client IP. Socks Proxy for Anonymous Browsing Let’s say I wanted to browse Ruby Sash Consulting, but I didn’t want my IP address of my client to show up in the logs. Others will check the application headers to verify that your 443 traffic is actually https, and not ssh. Some firewalls allow port 80 or port 443 traffic but not port 22.

Some firewalls also inspect traffic and will disallow ssh tunnels. Socks Proxy to Bypass Firewall If you are behind a firewall that doesn’t allow DNS or web browsing you can simply bypass it (assuming SSH IS allowed). Reasons to Use SSH Tunnel/Socks Proxyĭon’t count on a SSH Tunnel to bypass everything, but it has other uses too. The server will then relay any information you send it and connect to the final server like it came from your intermediary server instead of the client. One of the most common things to pass over an SSH Tunnel is web browsing data (SOCKs Proxy).īasically you will create a SSH Tunnel from your client to a remote server. You can create an encrypted channel, then pass data over that channel.

Buy ssh proxy