[WLUG] SSH and HTTP Proxy Options

[Dan Pritts]

Either solution is probably fine.  If your DMZ device is also your default route, an http proxy can be “transparent”; otherwise, clients will have to be configured for the proxy (regardless of socks vs. http proxy). 

http proxies can have some useful features (e.g., whitelists or blacklists of sites to view, caching, etc).   I’ve used “tinyproxy”, which has the advantage of being simple.

danno

> On Jun 23, 2015, at 2:35 PM, Chad Crabtree <flaxeater at gmail.com> wrote:
> 
> So I'm tasked with building a proxy that will route ssh and HTTP(s) through a public facing server into the safe side of the network to support developers.  My first thought was ssh socks proxy to get the job done, but I've been doing some research and it seems that it can be done through an HTTP proxy too, corkscrew is one I've seen so far.  
> 
> I was hoping I could take advantage of the wiser and more experienced among us for some alternatives?  
> 
> - Socks Proxy?
> - Http Proxy?
> - ????
> 
> Whats your suggestion, I have a private network with one computer in the DMZ (to restate it 'simply') and I need to allow N users to connect to their personal machine on the inside from anywhere.  
>