18.01.2019 21:08, Amos Jeffries пишет:
On 19/01/19 4:31 am, Alex Rousskov wrote:
On 1/18/19 4:35 AM, Dmitry Melekhov wrote:
17.01.2019 21:02, Alex Rousskov пишет:
On 1/16/19 10:30 PM, Dmitry Melekhov wrote:
2019/01/17 09:18:21 kid1| ERROR: negotiating TLS on FD 55:
error:14090086:SSL routine
On 1/20/19 3:04 PM, Eliezer Croitoru wrote:
> This swap.state behavior is only for UFS/AUFS cache_dir or also to rock?
Rock cache_dirs do not use swap.state.
Alex.
> -Original Message-
> From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On
> Behalf Of Alex Rousskov
On 1/20/19 3:02 PM, Eliezer Croitoru wrote:
> What's the best way to ban Let's encrypt based certificates? or
> whitelist a very narrow list of Root and Intermediates CA?
A requirement to ban all Let's Encrypt sites sounds invalid to me, but
you can use certificate validator to do that. Same for
You probably meant 4.5...
http://www1.ngtech.co.il/repo/centos/7/x86_64/squid-4.5-1.el7.x86_64.rpm
Eliezer
Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: elie...@ngtech.co.il
-Original Message-
From: squid-users [mailto:squid-users-boun...@lists.squid-c
Just to make sure:
This swap.state behavior is only for UFS/AUFS cache_dir or also to rock?
Thanks,
Eliezer
Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: elie...@ngtech.co.il
-Original Message-
From: squid-users [mailto:squid-users-boun...@lists.squid-
OK so from the real world:
What's the best way to ban Let's encrypt based certificates? or whitelist a
very narrow list of Root and Intermediates CA?
I have a setup which one of the requirements is to restrict access to sites
which depends on Let's encrypt generated certificates.
The issue is