Hi, sorry to reactivate this thread again. I understand fully the nature of the problem with HTTPS and transparent proxies, my question is about endian:
Most of the workarounds for this are simply to read what you can from the packet, (the source/destination addresses) and try to reverse DNS lookup the IP.
IF the IP reverses properly your cache device can apply a rule, or can simply apply a rule based on the source/dest IP's, but this will not prevent someone from sending their encrypted packets to a foreign proxy for further delivery.
Despite the remaining issues, this is actually what I am after (it is the right solution for the environment I want to deploy it into).
Could anyone tell me how easy it is to implement this with endian? (I.e. just do reverse DNS on the destination address, if it resolves to facebook (etc) domain on a given list - block it.)
Unless the very advanced ones, transparent proxies can't filter out HTTPS by default.
Other than by reverse IP, what other methods are transparent proxies doing?
The paid version of untangle webfilter seems to block HTTPS, but I think it is just doing reverse IP on the packets. Does anyone know for sure?
And again, my main question is how easy is it to setup a reverse DNS block on HTTPS traffic using endian?