Proxy HTTPs: Certificate not secure in Google Chrome how to upgrade to SHA-256?

[Guest]

[betojrjuarez]

Proxy HTTPs: Certificate not secure in Google Chrome how to upgrade to SHA-256?
I've been using Endian for 5 years on several clients.
I am migrating to version 3.2.2 mainly because of HTTPs proxy (authenticated proxy) but a problem is occurring in Google Chrome because of the HTTPs certificate that still uses SHA1 encryption, does anyone have any solution how to change it in Endian 3.2.2 for SHA256 or any other that works on Chrome?
Error showing in Chrome:
Your connection is not private
Invaders may be trying to steal your information from "site" (for example, passwords, messages or  cards). NET :: ERR_CERT_COMMON_NAME_INVALID

Note: In IE and Firefox browsers that still support SHA1 encryption the HTTPs proxy is working perfectly.

If anyone can help, I'm grateful.

[dda]

Came here to post this same question.

[Dark-Vex]

Hi, there is this issue opened on the bug tracker https://jira.endian.com/browse/UTM-1544 it's under testing. So I think it will be released in a few weeks on the community channel

[dda]

Thanks for the heads up.

[Dark-Vex]

They have placed the new Squid packages (which include also the SHA-256 fix) here:

https://jira.endian.com/browse/UTM-1564