HTTPS scanning Web Protection SSL error ERR_CERT_COMMON_NAME_INVALID

HI KarstenStolten, 

The new version of Chrome V58 will no longer accept certificates that do not have a subject alternate name.  Chrome is following RFC 2818 for this change.  Chrome V58 has now gone GA .

This could affect the Sophos Web appliance and Sophos UTM, which both use https scanning. The site generated certificate that we give back in these cases does not have a subject alternate name, meaning Chrome will reject the certificate and block the site

There are 3 options you may opt for. 

Option 1: Disable HTTPS scanning untill the issue is fixed. 

Option 2: Use another Web Browser . 

Option 3 *preferred: setting this GPO to ENABLED https://www.chromium.org/administrators/policy-list-3#EnableCommonNameFallbackForLocalAnchors 

Our Dev team are working on this issue should be resolved soon . 

HI KarstenStolten, 

The new version of Chrome V58 will no longer accept certificates that do not have a subject alternate name.  Chrome is following RFC 2818 for this change.  Chrome V58 has now gone GA .

This could affect the Sophos Web appliance and Sophos UTM, which both use https scanning. The site generated certificate that we give back in these cases does not have a subject alternate name, meaning Chrome will reject the certificate and block the site

There are 3 options you may opt for. 

Option 1: Disable HTTPS scanning untill the issue is fixed. 

Option 2: Use another Web Browser . 

Option 3 *preferred: setting this GPO to ENABLED https://www.chromium.org/administrators/policy-list-3#EnableCommonNameFallbackForLocalAnchors 

Our Dev team are working on this issue should be resolved soon . 

Do you have any experience applying that GPO? I must be missing something. I have the policies in GP Management Editor, but I cannot find the policy in question anywhere. 

I had the same issue. Took me a while to realise that I had to update the ASMX files with the new version (the files in the link were updated for the v58 release on 18th April). Update these and the entry is under User Admin Templates > Google > Chrome as 'Whether to allow certificates issued by local trust anchors that are missing the subjectAlternativeName extension'.

Thanks, I spent a good 10 minutes looking for that and had just given up!

Thank you for the info!

Looking forward to the resolution.

Kind regards
Karsten Stolten

Thanks Aditya for your post. Just to confirm that according to https://textslashplain.com/2017/03/10/chrome-deprecates-subject-cn-matching/ the EnableCommonNameFallbackForLocalAnchors setting will stop working in a later version of Chrome (quite a few months away, but still).

Hoping for a quick resolution for this from Sophos so that this isn't necessary any more.

Ηι

Any update regarding issue ?

Thank you very much for pointing that out!

Ηι

Any update regarding issue ?

Hello, I'm just wondering if there is any news on when we might see an update to resolve this issue?

As this is now starting to affect our organisation as well. We managed to stop the updates before our PCs were affected but a number of our Macs have already updated to Chrome 58 and can not get on Google websites and services.

Unfortunately Macs cannot use GPOs, so we have had to advise users to switch to Safari for the time being, but it would be better if Sophos could fix the issue with HTTPS certificate generation on their UTM system.

Thanks,

Dan Jackson (Lead ITServices Technician)

Long Road Sixth Form College

Cambridge, UK.

Hi All,

We have resolved this issue with our latest update 

UTM 9.413004

ftp://ftp.astaro.de/UTM/v9/up2date/u2d-sys-9.412002-413004.tgz.gpg

MD5: 753ff750ef6785f3f7fa2c97ed9da42c

File size: ~4MB