On 18/01/2016 10:13 a.m., Roman Gelfand wrote:
> I am not sure where I am going wrong here...
>
>
> ssl bump certificate
> openssl req -new -newkey rsa:2048 -sha256 -days 365 -nodes -x509 -keyout
> squidCA.pem -out squidCA.pem
>
> The der certificate was generated and deployed on client compute
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This is most probably client certificate error. IM or something. You can
ignore it if users not compliances.
18.01.16 3:13, Roman Gelfand пишет:
> I am not sure where I am going wrong here...
>
>
> ssl bump certificate
> openssl req -new -newkey r
I am not sure where I am going wrong here...
ssl bump certificate
openssl req -new -newkey rsa:2048 -sha256 -days 365 -nodes -x509 -keyout
squidCA.pem -out squidCA.pem
The der certificate was generated and deployed on client computer trusted
root
openssl x509 -in squidCA.pem -outform DER -out s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
No.
18.01.16 0:56, Roman Gelfand пишет:
> I am getting an error, below, in a cache.log. How can I identify the
> request associated with this error? It doesn't appear to be an issue with
> client-to-proxy. It seems like a problem with proxy-to-
I am getting an error, below, in a cache.log. How can I identify the
request associated with this error? It doesn't appear to be an issue with
client-to-proxy. It seems like a problem with proxy-to-remote_server.
Error negotiating SSL on FD 43: error:14090086:SSL
routines:SSL3_GET_SERVER_CERTIF
