Configuring VPN Remote Access for the first time on your Sophos XG Firewall? Check out this useful Community post!
We'd love to hear about it! Click here to go to the product suggestion community
Apple have changed the validity requirments of certificates as detailed here:
This has caused the transparent proxy on the UTM 9 to error on devices updated to IOS 13. Is there a way to configure or modify the man-in-the-middle certificate/template that is used by the UTM for automatically generated certificates to bring it into line with this new requirment?
From the quick checks I have done, it looks as though the issues are due to UTM issuing man-in-the-middle certs that are valid for 3 years, have a 1024 bit public keysize and do not have ExtendedKeyusage extension set to TLS Web Server Authentication.
Excerpt from the above article:
All TLS server certificates must comply with these new security requirements in iOS 13 and macOS 10.15:
Additionally, all TLS server certificates issued after July 1, 2019 (as indicated in the NotBefore field of the certificate) must follow these guidelines:
Connections to TLS servers violating these new requirements will fail and may cause network failures, apps to fail, and websites to not load in Safari in iOS 13 and macOS 10.15.
If anyone could point me to the location of the certificate template or mechanism of MIM certificate generation I would greatly appreciate it.
Edit: I have found a similar issue described in the XG forum. https://community.sophos.com/products/xg-firewall/f/intrusion-prevention/115171/ssl_scanning_certificate-not-accepted-under-ios-13
In reply to MichaelBeattie:
Me too it is 1024bit, not the supposed 2048bit.
Tested with the XG - here it works...
In reply to Jaydeep:
Apologies for not updating my own post. For context as to why I accepted this solution and haven't commented; I use XCA (Multi-platform GUI for OpenSSL) which I used to generate my SSL certs for home systems.
As I have a Root CA already installed and trusted on all my home systems, I created a Subordinate CA for Sophos UTM using the recommended settings in the Apple article. This allows me to change the UTM Cert without having to update all my client devices as they will automatically trust it as an Issuer.
I appreciate this may not help everyone.
I use XCA as it allows me to manage and backup all my certifcates as it uses its own password protected database.
Sophos need to update the Web Protection -> Filtering Options -> HTTPS CAs -> 'Regenerate' function to create 2048 bit keys for the certificate it uses from what has been described by fellow users.
I'm sure its a straight forward option in a stored Function somewhere in thier code.
In reply to Rax Ramjam:
I was wondering if anybody here has received any update on this from Sophos? I’m also having trouble with Apple devices which are running iOS 13.1.1 + and OSX 10.15. As others have stated here already, Apple have changed the requirements for certificates.
Has anybody been able to generate a certificate for Sophos UTM https scanning, using the Windows environment? I have a trusted Windows CA in my environment in which I’d like to use to generate a certificate, but having real trouble on making any progress.
In reply to RichardHughes1:
The issue has been reported as bug with ID NUTM-11345 (Regenerated Signing CA using 1024bit key, causing iOS 13 trust issues).
The fix is going to be released in the firmware version 9.7 MR1 (9.701).
Which is most probably going to be released around Jan 14.
In reply to Herrmannsdorfer:
I can confirm that UTM 9.701 includes the fix for
and does generate 2048 bit keys as required by Apple's new policies. One does of course need to regenerate the Signing CA and then distribute, but that is to be expected: Web Protection / Filtering Options / HTTPS CAs / Signing CA / Regenerate
In reply to Fahnoe:
Confirm - all well again. ;-)
I have exactly the same problem on my iPhone 11, especially when I try to navigate in heavy sites such as the Formula 1 website or movies 123, it is really annoying, but I understand that they have already been able to identify it and it is expected to be solved soon , hopefully, because it's really quite annoying to navigate like this