<div dir="ltr"><div><div>Yes, SSLBump still works with the web apps, but it would be a lot more convenient if the mobile apps would also work.<br><br></div>Does anyone know how to pin Squid's self-signed certificate's public key to Googledrive and Dropbox so that it would work with SSLBump enabled?<br><br></div>Stan<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 31, 2015 at 3:29 PM, Yuri Voinov <span dir="ltr"><<a href="mailto:yvoinov@gmail.com" target="_blank">yvoinov@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><span class="">
<br>
-----BEGIN PGP SIGNED MESSAGE----- <br>
Hash: SHA256 <br>
<br></span>
BTW, GoogleDrive web application still works with bump. Use it, Luke
;)<span class=""><br>
<br>
01.09.15 2:21, Jason Haar пишет:<br>
</span><span style="white-space:pre-wrap"><span class="">> On 01/09/15 02:59, Shane King
wrote:<br>
>> Accessing via the browser may work but the sync clients
that sit in<br>
>> the system tray use certificate pinning I believe. So if
certificate<br>
>> pinning is being used, ssl bumping will not work. You
will see an<br>
>> alert message in the pcap followed by a connection
termination.<br>
><br>
> This stopped working for me last week - I suspect there was
an update or<br>
> something<br>
><br>
> Really frustrating: one of the primary reasons I want to do
TLS<br>
> intercept is to AV all the viruses published on dropbox!!!<br>
><br>
> If the Cloud providers go full pinning, the future of TLS
Intercept is bleak<br>
><br>
><br>
><br>
><br></span><span class="">
> _______________________________________________<br>
> squid-users mailing list<br>
> <a href="mailto:squid-users@lists.squid-cache.org" target="_blank">squid-users@lists.squid-cache.org</a><br>
> <a href="http://lists.squid-cache.org/listinfo/squid-users" target="_blank">http://lists.squid-cache.org/listinfo/squid-users</a></span></span><span class=""><br>
<br>
-----BEGIN PGP SIGNATURE-----
<br>
Version: GnuPG v2
<br>
<br></span>
iQEcBAEBCAAGBQJV5LkrAAoJENNXIZxhPexGH9oH/AyK089Jek7yb/YPB16jAKPJ
<br>
LnKgKPQ4r8lu3wm5o4JuOXF6mun79fGVW9dymB5rasTJlHiCHrvXEK4G2KqyRg3B
<br>
57TdvHuLhHr+IE0jcpMpk6n/pbdHzYJwkbplTd9HNApw+/LJpfxXVzQZsspJJC58
<br>
e12pMXL+i5Dv2vEYLEeySVnDN0mtuBdxD7lxDWFDFDbfBZvoGHEptOQYR3lelEet
<br>
xEIds+sNYrjYPK8a9BuiKSK0IqQ5mxhsbUIg4Z7LxyKv3+sTV+aW3HMdKkMoc5t8
<br>
bPCHec1eIxU7p9lgyKGn2HXtV1WQ5MAeOuI9YHGqdeSfgCPfT1wYF2imiHC9ez8=
<br>
=2wPb
<br>
-----END PGP SIGNATURE-----
<br>
<br>
</div>
<br>_______________________________________________<br>
squid-users mailing list<br>
<a href="mailto:squid-users@lists.squid-cache.org">squid-users@lists.squid-cache.org</a><br>
<a href="http://lists.squid-cache.org/listinfo/squid-users" rel="noreferrer" target="_blank">http://lists.squid-cache.org/listinfo/squid-users</a><br>
<br></blockquote></div><br></div>