On 12/12/2015 6:05 p.m., Amos Jeffries wrote: > On 12/12/2015 10:55 a.m., George Hollingshead wrote: >> i am getting this message when trying to run my newly compiled squid >> 3.5.11. i think it's related to openssl but i'm really lost. >> >> Any incite on what's needed to correct this? i'm really determined to bump >> ssl so i can log them but it's becoming a pain for my skill level; lol >> >> Thanx >> >> FATAL: sign hash 'sha256' is not supported squid 3.5 >> > > There is no such error produced by Squid, and it looks nothing like an > OpenSSL message. Particularly saying "squid 3.5". Found it. There is one in Squid similar, but not quite the same wording you posted. It happens when OpenSSL is asked to translate the text hash name into it ID code for use, and OpenSSL returns an error. So yes, OpenSSL realeted. Either it needs an upgrade, or you rconfigured it not to understand SHA256. > > For anyone to help you will need to provide the full and exact error > message. Squid -v output, OS details, OpenSSL version details, > squid.conf, etc. That still applies. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
