-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
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 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
On 12/14/2015 09:16 PM, Amos Jeffries wrote:
With all that looking hopeful, and the certs identified as the secondary
chain being attached (everything except the firstprimary/signing cert).
I'm not actually finding anywhere sending the actual signing certificate
itself during the bumping
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all.
Does anybody can tell me - is it possible to use subordinate secondary
CA in squid for SSL Bumping purpose?
I.e., we have self-signed primary CA for issue subordinate CA,
subordinate CA we install in squid's setup,
primary CA
On 15/12/2015 10:26 a.m., Yuri Voinov wrote:
>
> Hi all.
>
> Does anybody can tell me - is it possible to use subordinate secondary
> CA in squid for SSL Bumping purpose?
>
> I.e., we have self-signed primary CA for issue subordinate CA,
>
> subordinate CA we install in squid's setup,
>
>
