by adrien » Jun 04 14 11:37 am
Hi
in your proxifier setup, what type of proxy is it configured to connect to? SOCKS? or maybe HTTP tunneling?
WinGate services have SOCKS client and HTTP tunneling client support built in, so they can connect directly to an upstream proxy.
But I think a bigger problem is using NAT for https. With https, if the client isn't using a proxy, then it expects to make a connection (usually port 443), then send a TLS/SSL client helo packet. This is not http, it's TLS/SSL first and after that http.
Due to the encryption, you can't intercept this, unless you use https inspection, and can install a trusted cert on the device? Probably not an option?
But you can use a TCP mapping proxy, intercept port 443, get it to connect out via a proxy using SOCKS or http tunneling upstream.
So I still think you don't need proxifier. Proxifier only supports SOCKS and HTTP tunneling as well. WinGate already has this, unless you are required to use SOCKS5 with auth.
Adrien