Hello,
I'm testing SSlBump and it works good, however I'm seeing something strange
with two proxies and x-forwarded enabled to the first, some requests are wrote
with the first proxy address.
user -> squid (fowarded_for on) -> squid (follow_x_forwarded_for allow all) ->
Net
Here log from th
On 15/09/2016 8:53 p.m., FredB wrote:
> Hello,
>
> I'm testing SSlBump and it works good, however I'm seeing something strange
> with two proxies and x-forwarded enabled to the first, some requests are
> wrote with the first proxy address.
>
> user -> squid (fowarded_for on) -> squid (follow_x
>
> Above are bumped requests sent inside the tunnel. Proxy #1 did not
> interact with them, so it has no way to add XFF headers.
>
> The SSL-Bump logic does not yet store some things like indirect
> client
> IP and associate them with the bumped requests.
>
> Amos
>
Ok thank you, there is a
On 15/09/2016 10:54 p.m., FredB wrote:
>
>>
>> Above are bumped requests sent inside the tunnel. Proxy #1 did not
>> interact with them, so it has no way to add XFF headers.
>>
>> The SSL-Bump logic does not yet store some things like indirect
>> client
>> IP and associate them with the bumped req
he eliezer
right now i moved from arm to intel
I’m using real pc
i will test the arm solution tomorrow .
for now i hope u can assist .
i got with ur advice and used now the store id solution .
but so far i have the hdd increase then suddenly decrease and so on
Thu 15 Sep 13:29:25 BST 2016
35
Hi,
For the Windows version of Squid from the good folks at Diladele, will it
ever preserve the squid.conf file when uninstalling and reinstalling
(upgrading)?
Thank you,
Patrick
___
squid-users mailing list
squid-users@lists.squid-cache.org
htt
Hi all ,
dear eliezer
i tried the NgTech solution on AMD cpu but the caching still 0 !!.
==
i have debian 64 bits
already had the bin file and moved to /usr/bin
root@debian:~# cat fetch-task.sh
#!/usr/bin/env bash
lockfile -r 0 /tmp/store-fetcher.lock
Hello Patrick,
Sorry I do not know. I guess MSI will just remove it.
So back it up somewhere before uninstall/install.
Best regards,
Rafael Akchurin
Diladele B.V.
BTW - new Docker build makes the native Windows Squid obsolete :)
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
15.09.2016 20:28, Rafael Akchurin пишет:
>
> Hello Patrick,
>
>
>
> Sorry I do not know. I guess MSI will just remove it.
>
> So back it up somewhere before uninstall/install.
>
This is easy and obvious procedure ;)
>
>
>
> Best regards,
>
> Ra
It's version 3.3.8
Sent from my Bell Samsung device over Canada's largest network.
Original message
From: erdosain9 Date:
2016-09-14 8:05 PM (GMT-07:00) To:
squid-users@lists.squid-cache.org Subject: Re: [squid-users] Cannot
get ACL to work
Hi.
What's your squid version?
So we are moving from an F5 LB to an AWS ELB. In the F5 we have a irule
that inserts a header that our origin servers looks for so they can return
https urls.
The ELB and Squid combination ends up rewritting the x_forward_proto header
from
HTTP_X_FORWARDED_PROTO: https
to
HTTP_X_FORWARDED_PROT
Dear, I've installed Squid3 with log rotation by default.
I've analyzed the /etc/logrotate.d/squid3 file, and I can see this lines:
postrotate
test ! -e /var/run/squid3.pid || /usr/sbin/squid3 -k rotate
endscript
Why is the reason of the "test ! -e /var/run/squid3.pid ||
/usr/sbi
Hello Yuri,
Yes latest Docker runs natively on Windows – you do not need to install
anything and so will happily run Squid in Docker container (inside hyper-v I
guess). See https://docs.docker.com/docker-for-windows/.
As for Squid 3.5.21 for Windows – will make installer for it in a couple of
*squid*-3.3.8
http://www.squid-cache.org/Versions/v3/3.3/cfgman/acl.html
This is suppose to be valid in squid-3.3.8
2016/09/15 09:18:02| FATAL: Invalid ACL type 'reg_header'
FATAL: Bungled /etc/squid/squid.conf line 21: acl CDKSSL reg_header
header-name ^HTTP_X_FORWARDED_PROTO: https
Thanks
On 09/15/2016 10:21 AM, Tory M Blue wrote:
> This is suppose to be valid in squid-3.3.8
>
> 2016/09/15 09:18:02| FATAL: Invalid ACL type 'reg_header'
You meant to type "req_header" instead of "reg_header".
> acl CDKSSL reg_header header-name ^HTTP_X_FORWARDED_PROTO: https
You are also misinter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
15.09.2016 22:04, Rafael Akchurin пишет:
>
> Hello Yuri,
>
>
>
> Yes latest Docker runs natively on Windows – you do not need to
install anything and so will happily run Squid in Docker container
(inside hyper-v I guess). See https://docs.docker
On 16/09/2016 3:39 a.m., Roberto Carna wrote:
> Dear, I've installed Squid3 with log rotation by default.
>
> I've analyzed the /etc/logrotate.d/squid3 file, and I can see this lines:
>
> postrotate
> test ! -e /var/run/squid3.pid || /usr/sbin/squid3 -k rotate
> endscript
>
> Why
On 16/09/2016 3:13 a.m., Tory M Blue wrote:
> So we are moving from an F5 LB to an AWS ELB. In the F5 we have a irule
> that inserts a header that our origin servers looks for so they can return
> https urls.
>
> The ELB and Squid combination ends up rewritting the x_forward_proto header
Squid d
Hi.
I have this problem with some webs
example:
https://www.dalemacartney.com/2012/07/06/squid-proxy-integration-with-active-directory-the-quick-and-simple-way/
The following error was encountered while trying to retrieve the URL:
https://www.dalemacartney.com/*
Failed to establish a secure
This is no error???
try_machine_keytab_princ: Trying to authenticate for squid-k$ from local
keytab...
-- try_machine_keytab_princ: Error: krb5_get_init_creds_keytab failed
(Preauthentication failed)
-- try_machine_keytab_princ: Authentication with keytab failed
-- try_machine_keytab_princ:
Read the whole section you referred to:
/tmp/.msktkrb5.conf-L8DxV8
-- reload: Reloading Kerberos Context
-- finalize_exec: SAM Account Name is: squid-k$
-- try_machine_keytab_princ: Trying to authenticate for squid-k$ from local
keytab...
-- try_machine_keytab_princ: Error: krb5_get_init_cred
Thank you very much. Sorry but ... also he authenticated with Kerberos ?? or
only Ldap ?? Because the important thing for me is Kerberos.
APOLOGY ignorance about it.
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/SSO-ldap-kerberos-tp4679470p4679542.html
S
On Thursday 15 Sep 2016 at 19:44, erdosain9 wrote:
> Hi.
> I have this problem with some webs
>
> example:
> https://www.dalemacartney.com/2012/07/06/squid-proxy-integration-with-activ
> e-directory-the-quick-and-simple-way/
> (71) Protocol error (TLS code: X509_V_ERR_CERT_HAS_EXPIRED)
> SSL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
16.09.2016 4:00, Antony Stone пишет:
> On Thursday 15 Sep 2016 at 19:44, erdosain9 wrote:
>
>> Hi.
>> I have this problem with some webs
>>
>> example:
>>
https://www.dalemacartney.com/2012/07/06/squid-proxy-integration-with-activ
>> e-direct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rotten year ago certificate - a terrible grief :)
16.09.2016 4:00, Antony Stone пишет:
> On Thursday 15 Sep 2016 at 19:44, erdosain9 wrote:
>
>> Hi.
>> I have this problem with some webs
>>
>> example:
>>
https://www.dalemacartney.com/2012/07
25 matches
Mail list logo
