1
votes

I'm trying to set up a proxy server that can handle both http and https traffic without prompting the browser about certificates (just like tunlr.net).

So far I've tried to use Squid and Nginx.

While handling regular http traffic is a walk in the park, https is proving very difficult.

Can anybody point me in the right direction?

2
Not really. All the "solutions" that I have seen about this subject require the end user to accept the proxy https certificate. Services like tunlr.net seem to return the original certificate of the tunneled website - Dave Ronsom
One of the main advantages of HTTPS is nobody can monitor traffic by listening in the middle. So the user definitely needs to "know" you're there. - dcaswell
If that's the case, than how do tunrl and unblock-us do it? I know it's possible, just not sure about the techniques used. - Dave Ronsom
It's not clear what you're trying to do, or whether this is a programming question at all. Squid handles normal HTTPS out of the box. If you want the original site's certificate, just use the normal HTTPS proxy method (not Squid's SSL Bump or Fiddler). If you're trying to implement this yourself, this question should give you an indication of what to do. - Bruno

2 Answers

0
votes

I think you should use a socks proxy not an http proxy, just like doing ssh tunnels, I used one on my vps, a package called dante the set up is kinda tricky but it really does the trick.

The package is available by default in ubuntu's repositories, and I assume probably other distros too.

Search on google on how to configure dante, and make sure you don't use a standard port, and even better use authentication to use the proxy, you don't want random people using your server as their proxy.

-1
votes

I just figured it out, turns out you don't need to set the https_port directive, only the http_port.