Hey Walter, I am not sure if it's the ssl_crtd which does such a thing but this is my main suspect. If you can extract the ssl_crtd binary from 3.4.X(newest) and test it before maybe Alex will respond then it will verify some of the doubt. Eliezer ---- Eliezer Croitoru Linux System Administrator Mobile: +972-5-28704261 Email: eliezer@xxxxxxxxxxxx -----Original Message----- From: squid-users [mailto:squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Walter H. Sent: Monday, May 16, 2016 7:48 PM To: squid-users@xxxxxxxxxxxxxxxxxxxxx Subject: SSL-Bump and generated certificates ... Hello, I updated squid 3.4.10 to 3.5.19 on my CentOS VM, I noticed that the generated certificates are now SHA2 and not SHA1, can I influence somewhere to generate still SHA1 certificates? (I have devices which use this proxy and are not able to handle SHA2) Thanks, Walter _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
