-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This looks like. Root CA doesn't send. Subordinate CA uses as signer for
mimicked. All and any clients got security alert.
16.12.15 1:38, Alex Rousskov пишет:
> On 12/14/2015 04:48 PM, Marcus Kool wrote:
>> On 12/14/2015 09:16 PM, Amos Jeffrie
Hey,
Basically what you want is called "reverse proxy".
Squid has this feature and you can see couple examples at the wiki:
http://wiki.squid-cache.org/FrontPage?action=fullsearch&context=180&value=reverse&titlesearch=Titles
This list is indeed squid users list but I will let you know that squid
Hi,
Thanks for the detailed response. I really appreciate it.
Unfortunately the load balancer we use is not a squid load balancer
and for now I will have to use HTCP.
Please take a look at the following lines from access.log of one of
the three squid servers.
1450351827.534 0 1
On 12/17/2015 03:12 AM, Yuri Voinov wrote:
> This looks like. Root CA doesn't send. Subordinate CA uses as signer for
> mimicked. All and any clients got security alert.
There may still be some terminology misunderstanding here because not
sending the root certificate is the right thing to do in
On 14.12.2015 22:26, Yuri Voinov wrote:
Hi all.
Does anybody can tell me - is it possible to use subordinate secondary
CA in squid for SSL Bumping purpose?
this is possible; I had this for several months this way;
I.e., we have self-signed primary CA for issue subordinate CA,
subordinate CA
On 18/12/2015 1:21 a.m., Sreenath BH wrote:
> Hi,
>
> Thanks for the detailed response. I really appreciate it.
>
> Unfortunately the load balancer we use is not a squid load balancer
> and for now I will have to use HTCP.
>
> Please take a look at the following lines from access.log of one of
>
On 17.12.2015 18:01, Alex Rousskov wrote:
On 12/17/2015 03:12 AM, Yuri Voinov wrote:
This looks like. Root CA doesn't send. Subordinate CA uses as signer for
mimicked. All and any clients got security alert.
There may still be some terminology misunderstanding here because not
sending the root
