<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>Accessing via the browser may work but the sync clients that sit in the system tray use certificate pinning I believe. So if certificate pinning is being used, ssl bumping will not work. You will see an alert message in the pcap followed by a connection termination.<div><br></div><div>-Shane</div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Stanford Prescott <stan.prescott@gmail.com> </div><div>Date: 8/31/2015 07:34 (GMT-07:00) </div><div>To: squid-users <squid-users@lists.squid-cache.org> </div><div>Subject: [squid-users] Dropbox and GoogleDrive apps won't connect with SSLBump enabled </div><div><br></div></div><div dir="ltr"><div><div>We have users of Squid 3.5.x with SSLBump enabled complaining about their DropBox and GoogleDrive apps not connecting. We are assuming this is related to the fact that these apps use HTTPS but they are not part of any of the browsers, therefor these apps do not have the sefl-signed certificate installed needed for SSLBump. <br><br>Has anyone successfully gotten these apps to connect with Squid's SSLBump enabled?<br><br></div>Regards,<br><br></div>Stan<br></div>
</body></html>