-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/12/2014 2:12 a.m., Yuri Voinov wrote:
Hi gents,
I found strange issue.
Squid 3.4.10. Intercept. HTTPS bumping. All works fine. All configs
correct.
Whenever all web https sites works perfectly - especially in
Chrome, most cloud
SSL Pinning? (I know Dropbox does this)
my two cents only :)
Raf
From: squid-users squid-users-boun...@lists.squid-cache.org on behalf of Yuri
Voinov yvoi...@gmail.com
Sent: Tuesday, December 30, 2014 2:12 PM
To: squid-users@lists.squid-cache.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
May be.
Does workaround exists?
30.12.2014 20:09, Rafael Akchurin ?:
SSL Pinning? (I know Dropbox does this)
my two cents only :)
Raf
From: squid-users squid-users-boun...@lists.squid-cache.org
On 12/12/2014 02:31 AM, Yu-Hsuan Liao wrote:
I'm trying to using Squid 3.5's new feature peek-and-splice to bypass
Skype connection
I'm a little confused about ssl_bump steps,
the wiki says that
peek Receive client (step SslBump1) or server (step SslBump2)
certificate while preserving the
Hello Yuri,
Luckily the same topic was just discussed on our forum – please see if this can
help
https://groups.google.com/d/msg/quintolabs-content-security-for-squid-proxy/GKIV3FpYSBE/9IET-4hg_tEJ
It describes the iptables settings for successful SSL bump exclusions for
Dropbox clients /
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Already found this lonely right post ;) I have Google-Fu too :) And it
longer than you :)
Anyway,
all of these issues solved.
I have snoop (not Windoze wireshark - all great things makes in console,
ya!) and take a look on single client traffic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sure.
Squid 3 WCCP key config part:
# WCCPv2 parameters
wccp2_router 192.168.200.2
wccp2_forwarding_method l2
wccp2_return_method l2
wccp2_service standard 0
wccp2_rebuild_wait off
wccp2_service standard 0
wccp2_service dynamic 70
Perfect thanks a lot!!!
Raf :)
From: Yuri Voinov [mailto:yvoi...@gmail.com]
Sent: Tuesday, December 30, 2014 9:23 PM
To: Rafael Akchurin; squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Squid 3 SSL bump: Google drive application could not
connect
-BEGIN PGP SIGNED MESSAGE-
Correction:
cache_dir rock /cache01/rock 5 120 256 max-size=31744
cache_dir aufs/cache01/aufs 200 4808 256 min-size=31745
cache_dir rock /cache02/rock 5 120 256 max-size=31744
cache_dir aufs/cache02/aufs 200 4808 256 min-size=31745
cache_dir rock /cache03/rock 5 120 256
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/12/2014 7:59 a.m., Markus Moeller wrote:
Hi Amos,
On 30/12/2014 3:31 p.m., Markus Moeller wrote:
Hi,
Can squid authenticate to an upstream proxy using digest ? If
I saw it right cache_peer allows basic and negotiate only (or
I thought it wasn't trivial, otherwise it would have been already done. ;-)
Thank you
Markus
Amos Jeffries wrote in message news:54a3416f.9060...@treenet.co.nz...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/12/2014 7:59 a.m., Markus Moeller wrote:
Hi Amos,
On 30/12/2014 3:31
On Dec 30, 2014 7:04 PM, Amos Jeffries squ...@treenet.co.nz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/12/2014 6:30 a.m., shawn wilson wrote:
On Dec 30, 2014 8:57 AM, Amos Jeffries wrote:
As bumping gets more popular we are hearing about a number of
services
Hey all,
Wondering if I could get some advice on potentially setting up a Squid
forward proxy on my network. I'm not a Linux novice by any means, but I'm
not experienced in server administration, log review, etc.
We're needing to deploy a simple non-caching, non-peering forward proxy to
integrate
13 matches
Mail list logo
