Maybe not exactly what you are looking for, but have you thought of using IPSec? You could deploy IPSec and encrypt every connection from your clients to the Proxy. I don't know what you are trying to achieve, but if your objective is to encrypt connections from the Clients to the proxy, IPSec would be perfectly transparent and scalable. On Sunday, December 12, 2010, purgat <purgatio@xxxxxxxxx> wrote: > Hi > I have seen similar discussions in the list in the past but none exactly > answers my question. > This is the setup I am looking for: > a server somewhere out there runs one or more instances of squid. > user at home sets up the browser to use the proxy. > whenever user puts an address in their browser address bar, request, is > encrypted with ssl and sent to squid. Instances (if more than one is > necessary) of squid then request the page through normal http from the > Internet and send the response through ssl back to the client. > Unfortunately the answers I have seen to this question in past seem to > ignore the fact that the user may want to use different websites. I > don't want just a couple of addresses to be accelerated by squid and > sent through ssl. What I am looking for is not a normal reverse proxy, > glorified with ssl. Unfortunately there is no example of such a setup in > wiki though I know a lot of people would want this set up for securing > data in their unsecure local network. The explanations on the web about > how to set this up come short of explaining a lot of things about an > already complex matter. > Is Squid able to help me with this? > By the way... ssh tunnelling is not an option for me. > > Regards > purgat > >
