OK,
I have tested a brand new 3.4.5 RPM that I have just built (not the one
that in the repo but from the same SRPM) and it works just fine.
1404244361.354 3 192.168.10.99 TCP_MISS/500 4054 GET
https://192.168.10.124:8443/favicon.ico - HIER_NONE/- text/html
To verify it against your settings:
https_port 8443 accel cert=/etc/squid/cloud.ngtech.co.il.crt
key=/etc/squid/cloud.ngtech.co.il.key
cipher=ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:RC4+RSA:+HIGH:+MEDIUM
options=NO_SSLv2 defaultsite=server_1.uk
You can download the public and private key at:
http://www1.ngtech.co.il/squid/cert.tar
it's not a valid certificate due to the expiration date but it was in
use until somewhere in 2013.
.. Stil runs.
My assumption is that instead of using a key and a certificate you are
using the CSR which is only the middle of the process to get a valid key.
All The Bests,
Eliezer
P.S. I am working on the 3.4.6 RPM for CentOS 6 and Oracle 6 and it will
be probably released next week.
On 07/01/2014 09:39 PM, Eliezer Croitoru wrote:
What is the output of "squid -v" when using 3.4.3?
I am not sure what the issue is and I can test it with my own
certificate later on.
If you see that I have not tested it yet in the next week try to send me
an email to remind me that it was not verified yet.
Eliezer
