On Friday, 9 October 2020 20:15:06 UTC+1, Yashar Vasegh wrote:
>
> Yes, it works, thank you. I still not understand why root CA cause problem
> here, but I was expecting for "Client side TLS AUTH" I need to add CA.
>
No: it's symmetrical.
* A server has a *server private key* and a *server certi
Yes, it works, thank you. I still not understand why root CA cause problem
here, but I was expecting for "Client side TLS AUTH" I need to add CA.
On Friday, October 9, 2020 at 12:40:16 PM UTC-4 b.ca...@pobox.com wrote:
> I suspect you may have misunderstood what a "CA Certificate" is. It's not
thank you for your response,
This is for ""Clients TLS" not "Server TLS", and the target url is not
google.com it is another server which supports "Clients tls". and even when
I change the (and if you change https://google.com to https://www.google.com
then
you get the search page) I get no re
I suspect you may have misunderstood what a "CA Certificate" is. It's not
the Certificate Signing Request (CSR) that you created for your own public
key. It's the public key of the certificate authority which signed the
server's certificate (i.e. google.com).
However, since google.com is sign
