Hi Alex
Can squid handle a slightly simpler case where we want to restrict
CONNECT access to servers which meet/fail to match a certain SSL cname?
eg I want to block facebook access, but without sslbump, so I allow SSL
proxying, but deny connections to servers with an SSL cname *.facebook.com?
On 02/09/2013 11:58 AM, Ed W wrote:
> On 20/01/2013 01:24, Amos Jeffries wrote:
>> On 19/01/2013 3:37 a.m., vincent viard wrote:
>>> I ask you about the feasibility of achieving an validation server
>>> certificates used during session establishment SSL/TLS in HTTPS at the
>>> level of SQUID proxy
On 20/01/2013 01:24, Amos Jeffries wrote:
On 19/01/2013 3:37 a.m., vincent viard wrote:
Hello,
I ask you about the feasibility of achieving an validation server
certificates used during session establishment SSL/TLS in HTTPS at the
level of SQUID proxy ?
The idea is not to break the SSL session
On 19/01/2013 3:37 a.m., vincent viard wrote:
Hello,
I ask you about the feasibility of achieving an validation server
certificates used during session establishment SSL/TLS in HTTPS at the
level of SQUID proxy ?
The idea is not to break the SSL session with a man-in-the-middle (ex.
SSLBump), bu
Hello,
I ask you about the feasibility of achieving an validation server
certificates used during session establishment SSL/TLS in HTTPS at the
level of SQUID proxy ?
The idea is not to break the SSL session with a man-in-the-middle (ex.
SSLBump), but to authenticate (and to authorize) the target
